Skip to content
https://darkreading.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
75
GRADE
C
FIX
2
REVIEW
2
PASS
5
INFO
0
Probed from Santa Clara, United States
301 Moved Permanently
Checks
9
5 PASS 2 REVIEW 2 FIX
F
IPv6 Readiness
Action
IPv6 records exist but unreachable
FIX
IPv6 records exist but unreachable
Warning::
IPv6 DNS records exist but server is not reachable
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Got: 2606:4700::6810:ddab, 2606:4700::6810:deab, 2606:4700::6810:dfab, 2606:4700::6810:e0ab, 2606:4700::6810:e1ab
Info::
IPv6 connection error
Got: dial tcp6 [2606:4700::6810:ddab]:443: connect: network is unreachable
IPv6 Misconfigured
AAAA Records 2606:4700::6810:ddab, 2606:4700::6810:deab, 2606:4700::6810:dfab, 2606:4700::6810:e0ab, 2606:4700::6810:e1ab Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
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
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 403 Expected: 301 redirect to HTTPS

www / non-www

200https://www.darkreading.com/
200https://darkreading.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

403http://darkreading.com/

HTTP version does not redirect to HTTPS

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

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: SJC)
Got: cf-ray: 9f078ed2aeae4b96-SJC
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9f078ed2aeae4b96-SJC
A+
DNS Records
5 A records, 8 ms lookup
PASS
5 A records, 8 ms lookup
Info::
Resolves to 5 IPv4 address(es)
Got: 104.16.221.171, 104.16.222.171, 104.16.223.171, 104.16.224.171, 104.16.225.171
Info::
Has 5 IPv6 (AAAA) record(s)
Got: 2606:4700::6810:ddab, 2606:4700::6810:deab, 2606:4700::6810:dfab, 2606:4700::6810:e0ab, 2606:4700::6810:e1ab
Info::
2 nameserver(s) configured
Got: ns1.ubmdns.com, ns2.ubmdns.com
Info::
2 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::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 8 ms
Got: 8 ms
A104.16.221.171, 104.16.222.171, 104.16.223.171, 104.16.224.171, 104.16.225.171
AAAA2606:4700::6810:ddab, 2606:4700::6810:deab, 2606:4700::6810:dfab, 2606:4700::6810:e0ab, 2606:4700::6810:e1ab
CNAME
NSns1.ubmdns.com, ns2.ubmdns.com
MX
10 us-smtp-inbound-2.mimecast.com
10 us-smtp-inbound-1.mimecast.com
TXT
MS=ms17477081
MS=ms41447875
MS=ms44788990
MS=ms62813886
google-site-verification=CrbTRNIj3fecxMfHLR0SlvqdF8n2ProsjOnXw5TcAa4
google-site-verification=RmY7DftliqtrwWVRvoYpyKyNXICeQvORa8D0uSvvkdQ
google-site-verification=TGEUCGu_ALeBVz8gKNRMVX9ANdFOv2y2C5bU3h-ujhE
google-site-verification=sUVJRoxhgiTGCs1tn14SqTGQTlYx0dSLlpSrY5Q8Cas
CAALookup not available with standard resolver
Resolved in 8 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.

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)

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

https://darkreading.com

29 ms · HTTP/1.1

301

https://www.darkreading.com/

61 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://darkreading.com30129 msHTTP/1.1cloudflare
2https://www.darkreading.com/20061 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 20 URLs
PASS
robots.txt present, sitemap with 20 URLs
Info::
robots.txt is present
Got: 1564 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 20 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1564 B Sitemaps referenced 14 User-agents Applebot-Extended, Cohere-ai, Omgili, PanguBot, *, Anthropic-ai, Bytespider, CCBot, Claude-Web, FacebookBot, Meta-ExternalAgent, Omgilibot, Amazonbot, AwarioRssBot, AwarioSmartBot, GPTBot, Magpie-crawler, Peer39_crawler, Timpibot, ClaudeBot, Diffbot, ImagesiftBot, Peer39_crawler/1.0, Webzio-Extended Blocking No — crawling allowed
User-agent: *
Sitemap: https://www.darkreading.com/sitemap.xml
Sitemap: https://www.darkreading.com/googlenews.xml
Sitemap: https://www.darkreading.com/contributors.xml
Sitemap: https://www.darkreading.com/generic-content.xml
Sitemap: https://www.darkreading.com/image-archive-index.xml
Sitemap: https://www.darkreading.com/news-archive-index.xml
Sitemap: https://www.darkreading.com/slideshows-archive-index.xml
Sitemap: https://www.darkreading.com/videos-archive-index.xml
Sitemap: https://www.darkreading.com/document-archive-index.xml
Sitemap: https://www.darkreading.com/podcast-archive-index.xml
Sitemap: https://www.darkreading.com/articles-archive-index.xml
Sitemap: https://www.darkreading.com/event-archive-index.xml
Sitemap: https://www.darkreading.com/multi-section-article-archive-index.xml
Sitemap: https://www.darkreading.com/sitemap-index.xml
Disallow: /search
Disallow: /recipe-portal/search
Disallow: /api/health
Disallow: /cdn-cgi/
Disallow: /live-preview/
Disallow: /my-purchases/
User-agent: Amazonbot
User-agent: Anthropic-ai
User-agent: Applebot-Extended
User-agent: AwarioRssBot
User-agent: AwarioSmartBot
User-agent: Bytespider
User-agent: CCBot
User-agent: ClaudeBot
User-agent: Claude-Web
User-agent: Cohere-ai
User-agent: Diffbot
User-agent: FacebookBot
User-agent: GPTBot
User-agent: ImagesiftBot
User-agent: Magpie-crawler
User-agent: Meta-ExternalAgent
User-agent: Omgili
User-agent: Omgilibot
User-agent: PanguBot
User-agent: Peer39_crawler
User-agent: Peer39_crawler/1.0
User-agent: Timpibot
User-agent: Webzio-Extended
Disallow: /
A
Domain Intelligence
darkreading.com — via SafeNames Ltd., 23 years, 1 months old, hosted on Cloudflare
PASS
darkreading.com — via SafeNames Ltd., 23 years, 1 months old, hosted on Cloudflare
Warning::
Domain expires in 85 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jul 17, 2026
Info::
DNSSEC is enabled
Info::
Registrar: SafeNames Ltd.
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: Cloudflare
Got: AS13335
Domain expiry

1 day

July 17, 2026

SSL certificate

75 days

Issued by Google Trust Services

Domain age

23 years, 1 months

Registered July 17, 2003

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

104.16.221.171

Registrar

SafeNames Ltd.

Unlocked 2 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 registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar SafeNames Ltd.
Created July 17, 2003 (23 years, 1 months ago)
Expires July 17, 2026 (2 months)
Last Updated July 17, 2025
Name Servers ns1.ubmdns.com, ns2.ubmdns.com
DNSSEC Enabled
Hosting
IP Address 104.16.221.171
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: rdap (0.2s)

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

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 28 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
7 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
4 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
10 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
28 ms
Total Time Total request time from DNS lookup through full response.
29 ms

Connection waterfall

DNS Lookup 7 ms TCP Connect 4 ms TLS Handshake 10 ms Server Processing 8 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