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

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
95
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
6 PASS 3 REVIEW
B
DNS Records
1 A records, 31 ms lookup
REVIEW
1 A records, 31 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 2.22.209.31
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a02:26f0:2380:28b::1f51, 2a02:26f0:2380:28a::1f51
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: www.nba.com-v1.edgekey.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: 31 ms
Got: 31 ms
A2.22.209.31
AAAA2a02:26f0:2380:28b::1f51, 2a02:26f0:2380:28a::1f51
CNAMEwww.nba.com-v1.edgekey.net
NS
MX
TXT
CAALookup not available with standard resolver
Resolved in 31 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

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
TLS Certificate Expiry & Recommendations
156 days until leaf cert expires — 5 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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
B
CDN & Delivery
Akamai
REVIEW
Akamai
Info::
Site is served via Akamai CDN
Got: x-akamai-transformed: 0 454991 0 -
CDN Detected: Akamai
Provider Akamai Evidence x-akamai-transformed: 0 454991 0 -
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.nba.com

https://www.nba.com

497 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.nba.com200497 msHTTP/1.1
A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2a02:26f0:2380:28b::1f51, 2a02:26f0:2380:28a::1f51
Got: 1 ms connect
IPv6 Ready
AAAA Records 2a02:26f0:2380:28b::1f51, 2a02:26f0:2380:28a::1f51 Connection Reachable (1 ms)
A+
Crawlability
robots.txt present, sitemap with 25 URLs
PASS
robots.txt present, sitemap with 25 URLs
Info::
robots.txt is present
Got: 2715 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 25 entries
Info::
Sitemap index with 25 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 2715 B Sitemaps referenced 1 User-agents *, Google-Extended, anthropic-ai, Applebot-Extended, ChatGPT-User, OAI-SearchBot, GPTBot, Amazonbot, CCBot, ClaudeBot, Claude-Web, Quora-Bot, PerplexityBot Blocking No — crawling allowed
Sitemap: https://www.nba.com/sitemap_index.xml

User-Agent: *
Disallow: /amp/
Disallow: /api/*
Disallow: /mediacentral/*
Disallow: /search
Disallow: /video/partners/
Disallow: /stats/events/ 
Disallow: /suns/tickets/vervelounge_requests.html
Disallow: /blazers/node/
Disallow: /bobcats/node/
Disallow: /bucks/node/
Disallow: /bulls/node/
Disallow: /cavaliers/node/
Disallow: /celtics/node/
Disallow: /clippers/node/
Disallow: /grizzlies/node/
Disallow: /hawks/node/
Disallow: /heat/node/
Disallow: /jazz/node/
Disallow: /kings/node/
Disallow: /knicks/node/
Disallow: /lakers/node/
Disallow: /magic/node/
Disallow: /mavericks/node/
Disallow: /nets/node/
Disallow: /nuggets/node/
Disallow: /pacers/node/
Disallow: /pelicans/node/
Disallow: /pistons/node/
Disallow: /raptors/node/
Disallow: /rockets/node/
Disallow: /sixers/node/
Disallow: /spurs/node/
Disallow: /suns/node/
Disallow: /thunder/node/
Disallow: /timberwolves/node/
Disallow: /warriors/node/
Disallow: /wizards/node/
Disallow: /blazers/users/
Disallow: /bobcats/users/
Disallow: /bucks/users/
Disallow: /bulls/users/
Disallow: /cavaliers/users/
Disallow: /celtics/users/
Disallow: /clippers/users/
Disallow: /grizzlies/users/
Disallow: /hawks/users/
Disallow: /heat/users/
Disallow: /jazz/users/
Disallow: /kings/users/
Disallow: /knicks/users/
Disallow: /lakers/users/
Disallow: /magic/users/
Disallow: /mavericks/users/
Disallow: /nets/users/
Disallow: /nuggets/users/
Disallow: /pacers/users/
Disallow: /pelicans/users/
Disallow: /pistons/users/
Disallow: /raptors/users/
Disallow: /rockets/users/
Disallow: /sixers/users/
Disallow: /spurs/users/
Disallow: /suns/users/
Disallow: /thunder/users/
Disallow: /timberwolves/users/
Disallow: /warriors/users/
Disallow: /wizards/users/

User-agent: GPTBot
Disallow: /
Allow: /standings
Allow: /schedule
Allow: /stats/help/glossary
Allow: /stats/draft/history
Allow: /stats/help/statminimums
Allow: /stats/history
Allow: /players
Allow: /player/*profile$
Allow: /team/*
Disallow: /team/*/schedule$

User-agent: Google-Extended
Disallow: /
Allow: /standings
Allow: /schedule
Allow: /stats/help/glossary
Allow: /stats/draft/history
Allow: /stats/help/statminimums
Allow: /stats/history
Allow: /players
Allow: /player/*profile$
Allow: /team/*
Disallow: /team/*/schedule$

User-agent: Amazonbot
Disallow: /

User-agent: anthropic-ai
Disallow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: ChatGPT-User
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: Claude-Web
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: GPTBot
Disallow: /

User-agent: OAI-SearchBot
Allow: /

User-agent: Quora-Bot
Disallow: /

User-agent: PerplexityBot
Disallow: /

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.nba.com/
301https://nba.com/

Preferred variant: www

HTTP → HTTPS

301http://www.nba.com/ https://www.nba.com/

Consistent

A+
Domain Intelligence
nba.com — via GoDaddy Corporate Domains, LLC, 31 years, 9 months old, hosted on Akamai
PASS
nba.com — via GoDaddy Corporate Domains, LLC, 31 years, 9 months old, hosted on Akamai
Info::
Domain registered until Nov 27, 2026 (7 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: GoDaddy Corporate Domains, LLC
Info::
Hosting: Akamai
Got: AS20940
Domain expiry

137 days

November 27, 2026

SSL certificate

156 days

Issued by DigiCert Inc

Domain age

31 years, 9 months

Registered November 28, 1994

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Akamai

ASN AS20940

96.17.207.30

Registrar

GoDaddy Corporate Domains, LLC

Lock status unknown 6 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 GoDaddy Corporate Domains, LLC
Created November 28, 1994 (31 years, 9 months ago)
Expires November 27, 2026 (7 months)
Last Updated October 28, 2025
Name Servers a1-148.akam.net, a12-65.akam.net, a16-64.akam.net, a18-65.akam.net, a5-65.akam.net, a7-67.akam.net
DNSSEC Not enabled
Hosting
IP Address 96.17.207.30
ASN AS20940 (AKAMAI-ASN1, NL)
Provider Akamai
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 760 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
34 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.
759 ms
Total Time Total request time from DNS lookup through full response.
761 ms

Connection waterfall

DNS Lookup 34 ms TCP Connect 1 ms TLS Handshake 3 ms Server Processing 722 ms Content Transfer 1 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback