Skip to content
https://nbcchicago.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 4 REVIEW
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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.nbcchicago.com/
200https://nbcchicago.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://nbcchicago.com/ → https://nbcchicago.com/

Consistent

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

Certificate validity

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

Recommended actions

  • 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: server header
CDN Detected: Akamai
Provider Akamai Evidence server header
A+
DNS Records
1 A records, 52 ms lookup
PASS
1 A records, 52 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 23.194.17.6
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
9 nameserver(s) configured
Got: use3.akam.net, asia3.akam.net, ns1-161.akam.net, aus1.akam.net, eur3.akam.net, usw1.akam.net, eur4.akam.net, asia2.akam.net, ns1-102.akam.net
Info::
4 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 52 ms
Got: 52 ms
A23.194.17.6
AAAA—
CNAME—
NSuse3.akam.net, asia3.akam.net, ns1-161.akam.net, aus1.akam.net, eur3.akam.net, usw1.akam.net, eur4.akam.net, asia2.akam.net, ns1-102.akam.net
MX
10 mxa-00176a04.gslb.pphosted.com
10 mxb-00176a04.gslb.pphosted.com
20 mx0b-00176a04.pphosted.com
20 mx0a-00176a04.pphosted.com
TXT
_t0z2q3kdxggdmd04iw7ihukwywrtado
SPF v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all
MS=ms59820124
CAALookup not available with standard resolver
Resolved in 52 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

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.

A
Redirect Chain
1 redirect(s), 182 ms total
PASS
1 redirect(s), 182 ms total
Info::
Single redirect
Got: https://nbcchicago.com → https://www.nbcchicago.com/ (301)
Info::
WWW normalization redirect

https://nbcchicago.com

6 ms · HTTP/1.1

301

https://www.nbcchicago.com/

176 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://nbcchicago.com3016 msHTTP/1.1AkamaiGHost
2https://www.nbcchicago.com/200176 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 208 URLs
PASS
robots.txt present, sitemap with 208 URLs
Info::
robots.txt is present
Got: 1874 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 208 entries
Info::
Sitemap index with 208 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1874 B Sitemaps referenced 4 User-agents Claude-Web, ClaudeBot, Scrapy, TurnitinBot, *, Amazonbot, anthropic-ai, AwarioRssBot, Bytespider, CCBot, ChatGPT-User, DataForSeoBot, FacebookBot, Google-Extended, GPTBot, news-please, peer39_crawler, PerplexityBot, AwarioSmartBot, Diffbot, magpie-crawler, NewsNow, omgili, omgilibot, peer39_crawler/1.0 Blocking No — crawling allowed
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
# Sitemap archive
Sitemap: https://www.nbcchicago.com/sitemap.xml

# Added by NBC AMP Update Plugin.
Allow: /.well-known/amphtml/apikey.pub

# Added by feeds.php
User-Agent: Amazonbot
Allow: /?partner=amazon-ai&rss=y*
Allow: /?rss=y&partner=amazon-ai*

User-Agent: *
Allow: /?rss=y&most_recent=y

# Added by update_robots_txt filter in functions
Disallow: /wp-content/uploads/sites/*/ninja-forms/*
Disallow: /?s=*
Disallow: /templates/nbc_partner_player_amp?*
Disallow: /results/*
Disallow: /topics?*
Disallow: /https*
Disallow: /includes/*.js

Disallow: /?cardId=*
Disallow: /liveblog/*/*
Disallow: /liveblog/*/?cardId=*

Sitemap: https://www.nbcchicago.com/sitemap.xml?type=video
Sitemap: https://www.nbcchicago.com/sitemap.xml?type=category
Sitemap: https://www.nbcchicago.com/sitemap-news.xml

# Query Parameter URLs to ignore
Disallow: *customize_changeset_uuid=
Disallow: *customize_autosaved=

# Added by Block LLMs Plugin
User-Agent: Amazonbot
Disallow: /

User-Agent: anthropic-ai
Disallow: /

User-Agent: AwarioRssBot
Disallow: /

User-Agent: AwarioSmartBot
Disallow: /

User-Agent: Bytespider
Disallow: /

User-Agent: CCBot
Disallow: /

User-Agent: ChatGPT-User
Disallow: /

User-Agent: Claude-Web
Disallow: /

User-Agent: ClaudeBot
Disallow: /

User-Agent: DataForSeoBot
Disallow: /

User-Agent: Diffbot
Disallow: /

User-Agent: FacebookBot
Disallow: /

User-Agent: Google-Extended
Disallow: /

User-Agent: GPTBot
Disallow: /

User-Agent: magpie-crawler
Disallow: /

User-Agent: news-please
Disallow: /

User-Agent: NewsNow
Disallow: /

User-Agent: omgili
Disallow: /

User-Agent: omgilibot
Disallow: /

User-Agent: peer39_crawler
Disallow: /

User-Agent: peer39_crawler/1.0
Disallow: /

User-Agent: PerplexityBot
Disallow: /

User-Agent: Scrapy
Disallow: /

User-Agent: TurnitinBot
Disallow: /
sitemap.xml 200 OK
Type Sitemap Index URLs 208 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
nbcchicago.com — via MarkMonitor Inc., 26 years, 6 months old, hosted on Akamai
PASS
nbcchicago.com — via MarkMonitor Inc., 26 years, 6 months old, hosted on Akamai
Info::
Domain registered until Feb 17, 2028 (1 years, 10 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.
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: Akamai
Got: AS16625
Domain expiry

612 days

February 17, 2028

SSL certificate

79 days

Issued by DigiCert Inc

Domain age

26 years, 6 months

Registered February 17, 2000

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Akamai

ASN AS16625

23.194.17.6

Registrar

MarkMonitor Inc.

Unlocked 9 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
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor Inc.
Created February 17, 2000 (26 years, 6 months ago)
Expires February 17, 2028 (1 years, 10 months)
Last Updated January 16, 2026
Name Servers asia2.akam.net, asia3.akam.net, aus1.akam.net, eur3.akam.net, eur4.akam.net, ns1-102.akam.net, ns1-161.akam.net, use3.akam.net, usw1.akam.net
DNSSEC Not enabled
Hosting
IP Address 23.194.17.6
ASN AS16625 (AKAMAI-AS - Akamai Technologies, Inc., US)
Provider Akamai
Data source: rdap (0.4s)

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

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more ▾

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A+
HTTP Probe Timing
Total 58 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
52 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.
58 ms
Total Time Total request time from DNS lookup through full response.
59 ms

Connection waterfall

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

Send Feedback