Skip to content
https://iheart.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
6 PASS 3 REVIEW
B
Redirect Chain
2 redirect(s), 296 ms total
REVIEW
2 redirect(s), 296 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.iheart.com/

https://iheart.com

7 ms · HTTP/1.1

301

https://www.iheart.com/

283 ms · HTTP/1.1

302

https://www.iheart.com/podcast/

5 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://iheart.com3017 msHTTP/1.1Varnish
2https://www.iheart.com/302283 msHTTP/1.1
3https://www.iheart.com/podcast/2005 msHTTP/1.1

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

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

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
322 days until leaf cert expires — 5 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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
A+
DNS Records
4 A records, 94 ms lookup
PASS
4 A records, 94 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 151.101.64.65, 151.101.192.65, 151.101.0.65, 151.101.128.65
Info::
No IPv6 (AAAA) records
Info::
6 nameserver(s) configured
Got: pdns196.ultradns.org, pdns196.ultradns.info, pdns196.ultradns.com, pdns196.ultradns.biz, pdns196.ultradns.net, pdns196.ultradns.co.uk
Info::
5 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: 94 ms
Got: 94 ms
A151.101.64.65, 151.101.192.65, 151.101.0.65, 151.101.128.65
AAAA—
CNAME—
NSpdns196.ultradns.org, pdns196.ultradns.info, pdns196.ultradns.com, pdns196.ultradns.biz, pdns196.ultradns.net, pdns196.ultradns.co.uk
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 alt4.aspmx.l.google.com
10 alt3.aspmx.l.google.com
TXT
tollbit-domain-verification=216394359d05a3916849d2e98043501b08ef65e32064b259d398...
_globalsign-domain-verification=jC79AL6jQMOo0_WuOPfUMCdwf0DdoS7HTwQTNCRcqa
google-site-verification=z-Ah2_PiN0t96l0dHDYP_9NOxat5DC5alquXgscboX0
_globalsign-domain-verification=OYfE_CcZQWFlEEOrR5yVCfCtmiQrm0bBdyUAJyg3qE
google-site-verification=p2FWrUKxtwBmQgHV4CjD80oKdZZBjmMNByoWvZMsYso
_globalsign-domain-verification=9Xqu2bonefjuoUF-XmyjAptAfuE-yStJz6wy9UnH-C
_globalsign-domain-verification=RQDNePcsBhiwiaGaUPKwwHamCQ-z-4EYJYovKcrwnK
google-site-verification=fILVA7r_w_Zfg9D2NQpBpJxXLIv50RGc11M1ux--Rz8
_globalsign-domain-verification=hif_fvCwz5dyl9ZePmzAgUQwJ5MREtuTErUOLtyTve
_globalsign-domain-verification=PNHrw0HP0dyqhb9jKVYye4MR49sVKcZt2vcZG-C7hJ
_globalsign-domain-verification=O81xyb7YxpdGeHWkniit_VBT4vTXz9__NFrNMoTwFg
google-site-verification=33v6HJw2o8cs7B7RhtG0i3eYrd_nU9-bsnewExsHyls
SPF v=spf1 ip4:207.230.136.140/29 ip4:207.230.157.126/29 mx a a:out-smtp.criticalmas...
_globalsign-domain-verification=0DuSsjDQZqNojSLYgubrV2cFBHjqsc6Ys64dxuGNmK
facebook-domain-verification=3e1i2n9vfc1x2rwk3g4ufvc9t9qk69
adobe-idp-site-verification=b7417ed1-3e0b-4349-aaea-1d2ce50df8a1
proxy-ssl.webflow.com
_globalsign-domain-verification=GKQxs_x8dYhPYSse4qFCmoTcpa0iNZRlq94zj_rSZz
_globalsign-domain-verification=5_rjWN2tj9-5abba8aZJedax0ElXvTJweWmisysoRn
_globalsign-domain-verification=3NjO4MTWauDfoFLenHAdtYNJugb1dUhcTjzveEaRlD
_globalsign-domain-verification=GXpUUS49HB9rYWZEmxJFtZdS61weLMlf91w9Dn-5O0
_dyg98hnit1xbhhko8z8xaknl64knr48
CAALookup not available with standard resolver
Resolved in 94 ms

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+
Crawlability
robots.txt present, sitemap with 367 URLs
PASS
robots.txt present, sitemap with 367 URLs
Info::
robots.txt is present
Got: 589 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 367 entries
Info::
Sitemap index with 367 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 589 B Sitemaps referenced 2 User-agents AmazonAdBot, Mediapartners-Google, facebookexternalhit, *, Googlebot-News Blocking No — crawling allowed
# Production
User-agent: AmazonAdBot
Allow: *

User-agent: Mediapartners-Google
Allow: /ads.txt

User-Agent: facebookexternalhit
Disallow: /_/
Disallow: /a/
Disallow: /misc/

User-agent: *
Disallow: /_/
Disallow: /a/
Disallow: /amp/
Disallow: /artist/*/now-playing
Disallow: /misc/
Disallow: /search*
Disallow: /library/*
Disallow: /*/itunes/
Disallow: /*/amazon/
Disallow: /sign-up/
Disallow: /login/
Disallow: /userInfo/
Disallow: /family-validation/

Sitemap: https://www.iheart.com/sitemap.xml

User-agent: *
User-agent: Googlebot-News
Sitemap: https://www.iheart.com/news_sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 367 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: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

302https://www.iheart.com/
200https://iheart.com/

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
iheart.com — via MarkMonitor Inc., 27 years, 8 months old, hosted on Fastly
PASS
iheart.com — via MarkMonitor Inc., 27 years, 8 months old, hosted on Fastly
Info::
Domain registered until Jan 7, 2027 (8 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: Fastly
Got: AS54113
Domain expiry

176 days

January 7, 2027

SSL certificate

322 days

Issued by GlobalSign nv-sa

Domain age

27 years, 8 months

Registered January 7, 1999

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Fastly

ASN AS54113

151.101.64.65

Registrar

MarkMonitor Inc.

Unlocked 7 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 January 7, 1999 (27 years, 8 months ago)
Expires January 7, 2027 (8 months)
Last Updated December 6, 2025
Name Servers ns0121.secondary.cloudflare.com, ns0237.secondary.cloudflare.com, pdns196.ultradns.biz, pdns196.ultradns.com, pdns196.ultradns.info, pdns196.ultradns.net, pdns196.ultradns.org
DNSSEC Not enabled
Hosting
IP Address 151.101.64.65
ASN AS54113 (FASTLY - Fastly, Inc., US)
Provider Fastly
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 42 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
38 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
0 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.
42 ms
Total Time Total request time from DNS lookup through full response.
42 ms

Connection waterfall

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

Send Feedback