Skip to content
https://rollingstone.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
1
REVIEW
7
PASS
9
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
9 PASS 7 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
C
Reverse DNS
Action
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR lookup failed for 192.0.66.114: lookup 192.0.66.114: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
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.rollingstone.com/
200https://rollingstone.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

59
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
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
A+
DNS Records
1 A records, 98 ms lookup
PASS
1 A records, 98 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 192.0.66.114
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-2007.awsdns-58.co.uk, ns-718.awsdns-25.net, ns-1426.awsdns-50.org, ns-416.awsdns-52.com
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 98 ms
Got: 98 ms
A192.0.66.114
AAAA—
CNAME—
NSns-2007.awsdns-58.co.uk, ns-718.awsdns-25.net, ns-1426.awsdns-50.org, ns-416.awsdns-52.com
MX
0 rollingstone-com.mail.protection.outlook.com
TXT
adobe-idp-site-verification=5f299ac5ccddedab8418f37aad62a1ff499e5979c3b247bd4229...
spf2.0/pra include:spf.protection.outlook.com ~all
globalsign-domain-verification=MT3LmRzGYPgORWLlSBkPpAUpBDH9kl8xxYmB6FjtjY
SPF v=spf1 include:spf.protection.outlook.com include:_spf.salesforce.com include:ma...
_globalsign-domain-verification=O81xyb7YxpdGeHWkniit_VBT4vTXz9__NFrNMoTwFg
tollbit-domain-verification=295db93fa4921634a8334a1c4c4ce22f2d04768d55ef46d50242...
atlassian-domain-verification=nprFKP7f9bTtDxCbcLk3c0Ag6DYYRzhq/pIp/XJkAvuuP9aQ2b...
pardot1033643=7091b62f85e62417b6a1797105e24cae130c04c780a60ecc73e1324d6b570573
google-site-verification=UVCh5ORO27hs1-UmThIy8gOYXeL9jiU8Z7eR2g0PxTY
facebook-domain-verification=un0pzjeye9ylufaptfim3y66d9h9lw
globalsign-domain-verification=qhllLTVNbc63_k7N_0u2VjkgHnq48qKQ8gKVvHWkHI
google-site-verification=vn4y0orqW_cUPEvrE0yaSdIGOIMJ4L-VxYkCkEF5shk
google-site-verification=7VABUHH6Rttvs3wGc7RIgeilrxB7Y17Jaq_Tu8w2rA8
google-site-verification=s5sbAg9TL-aEYCeHHTdGzEIjhQDYvbftbWNnI_7YhJE
MS=ms82822851
44325519CA
KDSIGvsMCjc7eS3DE46siVbZnGv+aCCw3bLnGHCgo73SH6ZTScPF1s+JMwoXiSuRgzv49wdzg38+bUdP...
CAALookup not available with standard resolver
Resolved in 98 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+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 23ms across 3 resolvers (spread 38ms)
PASS
Mean 23ms across 3 resolvers (spread 38ms)
Info::
Quad9: 2ms
Got: 2ms via 9.9.9.9:53
Info::
Cloudflare: 27ms
Got: 27ms via 1.1.1.1:53
Info::
Google: 40ms
Got: 40ms via 8.8.8.8:53
A
Redirect Chain
1 redirect(s), 17 ms total
PASS
1 redirect(s), 17 ms total
Info::
Single redirect
Got: https://rollingstone.com → https://www.rollingstone.com/ (301)
Info::
WWW normalization redirect

https://rollingstone.com

8 ms · HTTP/1.1

301

https://www.rollingstone.com/

8 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://rollingstone.com3018 msHTTP/1.1nginx
2https://www.rollingstone.com/2008 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 1253 URLs
PASS
robots.txt present, sitemap with 1253 URLs
Info::
robots.txt is present
Got: 1264 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1253 entries
Info::
Sitemap index with 1253 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1264 B Sitemaps referenced 2 User-agents GPTBot, Meta-ExternalFetcher, PerplexityBot, omgili, Applebot-Extended, ChatGPT-User, OAI-SearchBot, Diffbot, cXensebot, anthropic-ai, cohere-ai, Bytespider, CCBot, ClaudeBot, Claude-Web, FacebookBot, Google-Extended, ChatGPT, DeepSeekBot, Meta-ExternalAgent, Timpibot, Webzio-Extended, YouBot, *, omgilibot, DeepSeek Blocking No — crawling allowed
Sitemap: https://www.rollingstone.com/sitemap_index.xml
Sitemap: https://www.rollingstone.com/news-sitemap.xml
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
Disallow: /?s=
Disallow: /*/?s=
Disallow: /search/
Disallow: /search?
Disallow: *?v02
Disallow: *?replytocom
Disallow: /*preview=true
Disallow: /*theme_preview=true

User-agent: anthropic-ai
Disallow: /

User-agent: cohere-ai
Disallow: /

User-agent: omgili
Disallow: /

User-agent: omgilibot
Disallow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: ChatGPT-User
Disallow: /

User-agent: ChatGPT
Disallow: /

User-agent: DeepSeek
Disallow: /

User-agent: DeepSeekBot
Disallow: /

User-agent: GPTBot
Disallow: /

User-agent: OAI-SearchBot
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: Claude-Web
Disallow: /

User-agent: Diffbot
Disallow: /

User-agent: FacebookBot
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: Meta-ExternalAgent
Disallow: /

User-agent: Meta-ExternalFetcher
Disallow: /

User-agent: PerplexityBot
Disallow: /

User-agent: Timpibot
Disallow: /

User-agent: Webzio-Extended
Disallow: /

User-agent: YouBot
Disallow: /
User-agent: cXensebot
Crawl-delay: 5
sitemap.xml 200 OK
Type Sitemap Index URLs 1253 entries Valid XML Yes
Child Sitemaps:
A
Domain Intelligence
rollingstone.com — via CSC Corporate Domains, Inc., 32 years, 4 months old, hosted on WordPress.com (Automattic)
PASS
rollingstone.com — via CSC Corporate Domains, Inc., 32 years, 4 months old, hosted on WordPress.com (Automattic)
Warning::
Domain expires in 38 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Sep 20, 2026
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: CSC Corporate Domains, 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: WordPress.com (Automattic)
Got: AS2635
Domain expiry

34 days

September 20, 2026

SSL certificate

59 days

Issued by Let's Encrypt

Domain age

32 years, 4 months

Registered September 21, 1994

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

WordPress.com (Automattic)

ASN AS2635

192.0.66.114

Registrar

CSC Corporate Domains, Inc.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar CSC Corporate Domains, Inc.
Created September 21, 1994 (32 years, 4 months ago)
Expires September 20, 2026 (1 months)
Last Updated September 16, 2025
Name Servers ns-1426.awsdns-50.org, ns-2007.awsdns-58.co.uk, ns-416.awsdns-52.com, ns-718.awsdns-25.net
DNSSEC Not enabled
Hosting
IP Address 192.0.66.114
ASN AS2635 (AUTOMATTIC - Automattic, Inc, US)
Provider WordPress.com (Automattic)
Data source: rdap (0.4s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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 168 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
40 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.
5 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
169 ms
Total Time Total request time from DNS lookup through full response.
169 ms

Connection waterfall

DNS Lookup 40 ms TCP Connect 0 ms TLS Handshake 5 ms Server Processing 124 ms Content Transfer 0 ms
A+
CDN Cache Observability
Cache state: EXPIRED
PASS
Cache state: EXPIRED
Info::
CDN cache state observable via 1 header(s)
Got: x-cache=EXPIRED
A+
Health Check Endpoint
Health endpoint at https://rollingstone.com/health (HTTP 200)
PASS
Health endpoint at https://rollingstone.com/health (HTTP 200)
Info::
Public health endpoint at https://rollingstone.com/health
Got: https://rollingstone.com/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback