Skip to content
https://cfr.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
93
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
6 PASS 3 REVIEW
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.cfr.org/
200https://cfr.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://cfr.org/ → https://cfr.org/

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

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • 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
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9eff424b1e88f1a4-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9eff424b1e88f1a4-CDG
A+
DNS Records
2 A records, 121 ms lookup
PASS
2 A records, 121 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.8.238, 104.18.9.238
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700::6812:8ee, 2606:4700::6812:9ee
Info::
2 nameserver(s) configured
Got: wren.ns.cloudflare.com, nash.ns.cloudflare.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::
SPF record present in TXT
Info::
DNS resolution time: 121 ms
Got: 121 ms
A104.18.8.238, 104.18.9.238
AAAA2606:4700::6812:8ee, 2606:4700::6812:9ee
CNAME—
NSwren.ns.cloudflare.com, nash.ns.cloudflare.com
MX
10 mailstream-west.mxrecord.io
10 mailstream-east.mxrecord.io
TXT
rg8hd5ggho6acqinfo8hf5jpch
google-site-verification=tliseqBiVgyMcUgZ6TEOASSX0tR_CIfYytRcpSkgdQE
96klj2nvbp34j37cd47oed71oj
cloudflare-verify.cfr.org=196494934-324734179
yahoo-verification-key=FteV/VTlpDZDqVOz0nfUh/dna81sPJti1r92T7OvJbE=
anthropic-domain-verification-qbka3b=YFKxA6qLEUKvBhWEglq9Qonho
atlassian-domain-verification=mkphzoZsJONqMhVgOOTDKDSrHvIDpYeUTpK23cjB78ISYKULQB...
google-site-verification=hR8_4f5KbVXXAPKFcRxqE7Pc0edLt-r45B03EiYdix0
ektg3bp4gn38pns014i20q4qt0
fsti0cmu3t4aptsfm31jn5bro1
logmein-verification-code=7834021a-71ac-4eb4-9e6b-a4a966343d40
SPF v=spf1 include:aspmx.sailthru.com ip4:142.44.78.201 ip4:52.226.63.6 include:spf....
adobe-idp-site-verification=cf7feba8f9153bc715e02436f65e529e8562d492742e51f9b23d...
canva-site-verification=vqo8Y2fLzUfXxgvDB4SAtw
j755048pm7gb0nt9g3vdoqum51
google-site-verification=Q2QvuqLQqUQJYosH6Qb0dd4y3dpd8_tSVpIC39sSgzc
google-site-verification=iRRlDPJDQi5sRPOf305nX5nsKNcpyB2T0TAb5q47QtY
ptib1krhouoq6f2b5i74nnrpme.
atlassian-sending-domain-verification=f32762d3-0611-44b5-93f0-6dc018bcfac9
CAALookup not available with standard resolver
Resolved in 121 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
Redirect Chain
1 redirect(s), 489 ms total
PASS
1 redirect(s), 489 ms total
Info::
Single redirect
Got: https://cfr.org → https://www.cfr.org/ (301)
Info::
WWW normalization redirect

https://cfr.org

58 ms · HTTP/1.1

301

https://www.cfr.org/

431 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://cfr.org30158 msHTTP/1.1cloudflare
2https://www.cfr.org/200431 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700::6812:8ee, 2606:4700::6812:9ee
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700::6812:8ee, 2606:4700::6812:9ee Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 10 URLs
PASS
robots.txt present, sitemap with 10 URLs
Info::
robots.txt is present
Got: 2328 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 10 entries
Info::
Sitemap index with 10 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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 2328 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
# robots.txt
#
# This file is to prevent the crawling and indexing of certain parts
# of your site by web crawlers and spiders run by sites like Yahoo!
# and Google. By telling these "robots" where not to go on your site,
# you save bandwidth and server resources.
#
# For more information about the robots.txt standard, see:
# http://www.robotstxt.org/robotstxt.html

User-agent: *
Disallow: /search
Disallow: /_next/static/

Disallow: /wp-admin/
Disallow: /wp-includes/
Disallow: /wp-json/
Disallow: /wp-content/plugins/
Disallow: /wp-content/cache/
Disallow: /wp-content/themes/
Disallow: /trackback/
Disallow: /feed/
Disallow: /comments/
Disallow: /member
Disallow: /login

########################################
#        OLD ROBOTS.TXT CONTENT        #
# Keep it until we have drupal running #
########################################
# CSS, JS, Images
Allow: /core/*.css$
Allow: /core/*.css?
Allow: /core/*.js$
Allow: /core/*.js?
Allow: /core/*.gif
Allow: /core/*.jpg
Allow: /core/*.jpeg
Allow: /core/*.png
Allow: /core/*.svg
Allow: /profiles/*.css$
Allow: /profiles/*.css?
Allow: /profiles/*.js$
Allow: /profiles/*.js?
Allow: /profiles/*.gif
Allow: /profiles/*.jpg
Allow: /profiles/*.jpeg
Allow: /profiles/*.png
Allow: /profiles/*.svg
# Directories
Disallow: /core/
Disallow: /profiles/
# Files
Disallow: /README.md
Disallow: /composer/Metapackage/README.txt
Disallow: /composer/Plugin/ProjectMessage/README.md
Disallow: /composer/Plugin/Scaffold/README.md
Disallow: /composer/Plugin/VendorHardening/README.txt
Disallow: /composer/Template/README.txt
Disallow: /modules/README.txt
Disallow: /sites/README.txt
Disallow: /themes/README.txt
Disallow: /web.config
# Paths (clean URLs)
Disallow: /admin/
Disallow: /comment/reply/
Disallow: /filter/tips
Disallow: /node/add/
Disallow: /search/
Disallow: /user/register
Disallow: /user/password
Disallow: /user/login
Disallow: /user/logout
Disallow: /media/oembed
Disallow: /*/media/oembed
# Paths (no clean URLs)
Disallow: /index.php/admin/
Disallow: /index.php/comment/reply/
Disallow: /index.php/filter/tips
Disallow: /index.php/node/add/
Disallow: /index.php/search/
Disallow: /index.php/user/password
Disallow: /index.php/user/register
Disallow: /index.php/user/login
Disallow: /index.php/user/logout
Disallow: /index.php/media/oembed
Disallow: /index.php/*/media/oembed
sitemap.xml 200 OK
Type Sitemap Index URLs 10 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
cfr.org — via Network Solutions, LLC, 33 years, 3 months old
PASS
cfr.org — via Network Solutions, LLC, 33 years, 3 months old
Info::
Domain registered until Jul 6, 2028 (2 years, 2 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: Network Solutions, 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.
Domain expiry

720 days

July 6, 2028

SSL certificate

79 days

Issued by Google Trust Services

Domain age

33 years, 3 months

Registered July 7, 1993

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700::6812:8ee

Registrar

Network Solutions, LLC

Unlocked 2 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 Network Solutions, LLC
Created July 7, 1993 (33 years, 3 months ago)
Expires July 6, 2028 (2 years, 2 months)
Last Updated January 17, 2025
Name Servers nash.ns.cloudflare.com, wren.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700::6812:8ee
Data source: rdap (0.6s)

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

Connection waterfall

DNS Lookup 37 ms TCP Connect 16 ms TLS Handshake 24 ms Server Processing 19 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