A
Infrastructure report cardTop 50K site

usa.gov

89 out of 10015 passed3 to improve1 problems
Checked yesterday· Grading…
HTTPS & TLSA
Certificate, protocol, redirect, HSTS91
DNSA
Name servers, DNSSEC, CAA, registration86
EmailA
SPF, DMARC, MTA-STS, DKIM85
Web & networkA+
Security headers, IPv6, RPKI100
DependenciesB
How much hangs on one company80

HTTPS & TLS

91/100A
  • HTTP → HTTPS0/3

    http://usa.gov serves the site without encryption instead of redirecting to HTTPS.

    Answer every plain-HTTP request with a 301 redirect to the same address on https://.

  • HTTPS certificateLet's Encrypt10/10

    HTTPS with a valid certificate from Let's Encrypt.

  • Certificate expiry824/4

    The certificate is valid for another 82 days.

  • TLS versionTLS 1.34/4

    Negotiates TLS 1.3, the current protocol: faster handshakes, forward secrecy always.

  • Old protocols3/3

    Refuses the retired TLS 1.0 and 1.1.

  • Key strengthRSA 40962/2

    A strong key: RSA 4096.

  • HSTS1 year · preload4/4

    HSTS tells browsers to use HTTPS only, for 1 year.

  • HTTP/2 and HTTP/3HTTP/22/2

    HTTP/2.

DNS

86/100A
  • CAA records0/2

    No CAA records: any certificate authority may issue certificates for the domain.

  • Name servers54/4

    5 name servers for the domain.

  • Name servers answer5/55/5

    Every name server answers for the domain, with the same version of the zone.

  • DNSSECRSASHA2563/3

    Signed with DNSSEC: resolvers can tell forged answers from real ones.

Email

85/100A
  • Null MX0/1

    No MX records, and no null MX to say the domain takes no mail.

  • DKIM

    No DKIM key at the common selectors; it may use one that cannot be guessed.

  • SPF~all4/5

    SPF lists the servers allowed to send its mail and marks the rest as suspicious (~all).

  • DMARCreject7/7

    DMARC tells receivers to reject mail that fakes the domain (p=reject).

Web & network

100/100A+
  • Security headers

    The website answered 404 to the check (bot protection, most likely), so its headers are not graded.

  • IPv64/4

    usa.gov is reachable over IPv6 as well as IPv4.

  • RPKIvalid4/4

    The route to the website is RPKI-valid: networks can reject hijacked announcements of it.

Dependencies

80/100B
  • DNS providersgsa.gov3/5

    All DNS is with one provider (gsa.gov): an outage there takes the domain offline, as Dyn's did in 2016.

  • One company for everything5/5

    The website, DNS and email do not all hang on one company.

Who runs it

Website
Amazon Web Services
DNS
gsa.gov
Email
—

Routes

  • 23.22.0.0/15AS14618RPKI valid
  • 2600:1f18::/35AS14618RPKI valid

Name servers

  • dns.gsa.govAS16509
  • dns2.gsa.govAS16509
  • dns3.gsa.govAS16509
  • dns4.gsa.govAS16509
  • dns5.gsa.govAS16509

README badge

Show the grade in your README or docs; it updates when the domain is graded again.

usa.gov: A
[![Infrastructure grade](https://skycisa.com/grade/usa.gov/badge.svg)](https://skycisa.com/grade/usa.gov)

Compare with…

Full lookup
What is graded
HTTPS & TLS · 25%

A valid certificate (an invalid one means F), its expiry against its lifetime, TLS 1.3, no TLS 1.0/1.1 (else at most B), http:// sent straight to https://, HSTS, HTTP/2.

DNS · 20%

At least two name servers that all answer and agree, DNSSEC, CAA records, and a registration that is not about to expire.

Email · 20%

SPF, a DMARC policy that rejects forgeries (none means at most B), MTA-STS and TLS reporting for domains that take mail, DKIM at common selectors.

Web & network · 20%

Content Security Policy, nosniff, framing protection, Referrer- and Permissions-Policy, IPv6, and an RPKI-valid route (invalid means at most C).

Dependencies · 15%

DNS from more than one provider, and the website, DNS and email not all with one company.

A+ 95–100 · A 85–94 · B 75–84 · C 65–74 · D 50–64 · F below 50