Skip to content
https://realclearpolitics.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 3 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.

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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 190 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 190 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /dev/
Disallow: /concepts/
Disallow: /share/
Disallow: /fast/
Disallow: /galleries/
Disallow: /mockup/
Disallow: /mockups/
Disallow: /html_tests/
Disallow: /florida/

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

311
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
  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • 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
1 A records, 38 ms lookup
PASS
1 A records, 38 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 66.240.200.101
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
6 nameserver(s) configured
Got: ns10.dnsmadeeasy.com, ns14.dnsmadeeasy.com, ns15.dnsmadeeasy.com, ns13.dnsmadeeasy.com, ns11.dnsmadeeasy.com, ns12.dnsmadeeasy.com
Info::
1 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: 38 ms
Got: 38 ms
A66.240.200.101
AAAA
CNAME
NSns10.dnsmadeeasy.com, ns14.dnsmadeeasy.com, ns15.dnsmadeeasy.com, ns13.dnsmadeeasy.com, ns11.dnsmadeeasy.com, ns12.dnsmadeeasy.com
MX
0 realclearpolitics-com.mail.protection.outlook.com
TXT
_globalsign-domain-verification=SQONiBgTxRVzPPtIHjei_IUGCiAa0KxoVWFw1QfVes
google-site-verification=nYB5mMrdorF8Ke9PdB5sh5-SWjtsH1-8qLODxAUKj5c
MS=ms31851780
SPF v=spf1 include:spf.protection.outlook.com include:authsmtp.com include:_spf.sale...
google-site-verification=6uE7jYDZkSJHITSBhBcC8flH4IC_pgYUy18OCH1un6Y
stripe-verification=02d2b15ddabcadb61d15dc2c3fdb2b039142ea3b4144f9a0538e0c105bb7...
CAALookup not available with standard resolver
Resolved in 38 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), 704 ms total
PASS
1 redirect(s), 704 ms total
Info::
Single redirect
Got: https://realclearpolitics.com → https://www.realclearpolitics.com/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 704 ms total
Got: 704 ms

https://realclearpolitics.com

588 ms · HTTP/1.1

301

https://www.realclearpolitics.com/

116 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://realclearpolitics.com301588 msHTTP/1.1
2https://www.realclearpolitics.com/403116 msHTTP/1.1CloudFront

See the visual redirect chain in the HTTP Probe tab →

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

403https://www.realclearpolitics.com/
200https://realclearpolitics.com/

HTTP → HTTPS

301http://realclearpolitics.com/ https://realclearpolitics.com/

Consistent

A+
Domain Intelligence
realclearpolitics.com — via GoDaddy.com, LLC, 26 years, 7 months old, hosted on CARINET - CariNet, Inc., US
PASS
realclearpolitics.com — via GoDaddy.com, LLC, 26 years, 7 months old, hosted on CARINET - CariNet, Inc., US
Info::
Domain registered until Feb 3, 2028 (1 years, 9 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.com, LLC
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: CARINET - CariNet, Inc., US
Got: AS10439
Domain expiry

567 days

February 3, 2028

SSL certificate

311 days

Issued by GoDaddy.com, Inc.

Domain age

26 years, 7 months

Registered February 3, 2000

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

CARINET - CariNet, Inc., US

ASN AS10439

66.240.200.101

Registrar

GoDaddy.com, LLC

Unlocked 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
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar GoDaddy.com, LLC
Created February 3, 2000 (26 years, 7 months ago)
Expires February 3, 2028 (1 years, 9 months)
Last Updated September 8, 2022
Name Servers ns10.dnsmadeeasy.com, ns11.dnsmadeeasy.com, ns12.dnsmadeeasy.com, ns13.dnsmadeeasy.com, ns14.dnsmadeeasy.com, ns15.dnsmadeeasy.com
DNSSEC Not enabled
Hosting
IP Address 66.240.200.101
ASN AS10439 (CARINET - CariNet, Inc., US)
Provider CARINET - CariNet, Inc., US
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

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

Connection waterfall

DNS Lookup 47 ms TCP Connect 146 ms TLS Handshake 294 ms Server Processing 147 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