Skip to content
https://www.nfl.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Madrid, Spain
307 Temporary Redirect
Checks
9
5 PASS 4 REVIEW
B
DNS Records
4 A records, 24 ms lookup
REVIEW
4 A records, 24 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 151.101.129.55, 151.101.65.55, 151.101.1.55, 151.101.193.55
Info::
No IPv6 (AAAA) records
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: h3.nfl.map.fastly.net
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 24 ms
Got: 24 ms
A151.101.129.55, 151.101.65.55, 151.101.1.55, 151.101.193.55
AAAA—
CNAMEh3.nfl.map.fastly.net
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 24 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

B
Redirect Chain
2 redirect(s), 324 ms total
REVIEW
2 redirect(s), 324 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.

https://www.nfl.com

5 ms · HTTP/1.1

307

https://www.nfl.com/international/

5 ms · HTTP/1.1

308

https://www.nfl.com/international

314 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.nfl.com3075 msHTTP/1.1istio-envoy
2https://www.nfl.com/international/3085 msHTTP/1.1istio-envoy
3https://www.nfl.com/international200314 msHTTP/1.1istio-envoy

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
TLS Certificate Expiry & Recommendations
40 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

40
days left
0d 30d 60d 90d+

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
Crawlability
robots.txt present, sitemap with 73 URLs
PASS
robots.txt present, sitemap with 73 URLs
Info::
robots.txt is present
Got: 344 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 73 entries
Info::
Sitemap index with 73 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 344 B Sitemaps referenced 1 User-agents *, Mediapartners-Google Blocking No — crawling allowed
User-agent: *
Disallow: /_ctv/
Disallow: /_fantasy-app/
Disallow: /_libraries/
Disallow: /_mobile-app/
Disallow: /_mobileview/
Disallow: /_phs/
Disallow: /_sponsors/
Disallow: /account/
Disallow: /nfl-films-beta/
Disallow: /search/
Sitemap: https://www.nfl.com/sitemap-index.xml

User-agent: Mediapartners-Google
Disallow: /stats/player-stats/*
sitemap.xml 200 OK
Type Sitemap Index URLs 73 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.nfl.com/
301https://nfl.com/

Preferred variant: www

HTTP → HTTPS

301http://www.nfl.com/ → https://www.nfl.com/

Consistent

A+
Domain Intelligence
nfl.com — via MarkMonitor Inc., 30 years, 3 months old, hosted on Fastly
PASS
nfl.com — via MarkMonitor Inc., 30 years, 3 months old, hosted on Fastly
Info::
Domain registered until May 21, 2027 (1 years, 1 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: MarkMonitor Inc.
Info::
Hosting: Fastly
Got: AS54113
Domain expiry

313 days

May 21, 2027

SSL certificate

40 days

Issued by Let's Encrypt

Domain age

30 years, 3 months

Registered May 20, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Fastly

ASN AS54113

151.101.129.55

Registrar

MarkMonitor Inc.

Lock status unknown 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
Registrar MarkMonitor Inc.
Created May 20, 1996 (30 years, 3 months ago)
Expires May 21, 2027 (1 years, 1 months)
Last Updated April 19, 2025
Name Servers udns1.ultradns.net, udns2.ultradns.net
DNSSEC Not enabled
Hosting
IP Address 151.101.129.55
ASN AS54113 (FASTLY - Fastly, Inc., US)
Provider Fastly
Data source: rdap (0.3s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

A+
HTTP Probe Timing
Total 192 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
47 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
3 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
192 ms
Total Time Total request time from DNS lookup through full response.
192 ms

Connection waterfall

DNS Lookup 47 ms TCP Connect 1 ms TLS Handshake 3 ms Server Processing 141 ms Content Transfer 0 ms
A
CDN & Delivery
Fastly (MISS, MISS, MISS)
PASS
Fastly (MISS, MISS, MISS)
Info::
Site is served via Fastly CDN
Got: x-served-by: cache-iad-kcgs7200038-IAD, cache-iad-kiad7000091-IAD, cache-toj-leto2350053-TOJ
Info::
CDN cache status: MISS, MISS, MISS
CDN Detected: Fastly
Provider Fastly Cache Status MISS, MISS, MISS Evidence x-served-by: cache-iad-kcgs7200038-IAD, cache-iad-kiad7000091-IAD, cache-toj-leto2350053-TOJ
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback