Skip to content
https://rfc-editor.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
94
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.rfc-editor.org/
200https://rfc-editor.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://rfc-editor.org/ → https://www.rfc-editor.org/

Consistent

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

Certificate validity

37
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: CDG)
Got: cf-ray: 9efea33a9cbaf1ac-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9efea33a9cbaf1ac-CDG
A+
DNS Records
2 A records, 50 ms lookup
PASS
2 A records, 50 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.20.81, 104.18.21.81
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700::6812:1451, 2606:4700::6812:1551
Info::
2 nameserver(s) configured
Got: ken.ns.cloudflare.com, jill.ns.cloudflare.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: 50 ms
Got: 50 ms
A104.18.20.81, 104.18.21.81
AAAA2606:4700::6812:1451, 2606:4700::6812:1551
CNAME—
NSken.ns.cloudflare.com, jill.ns.cloudflare.com
MX
0 mail2.ietf.org
TXT
SPF v=spf1 ip4:166.84.6.31 ip4:166.84.7.238 ip6:2602:f977:800:f7f6::/64 ip4:166.84.7...
google-site-verification=S7F2LDRmYAIwFs4JZtnDdmZH23mNreKn8qKn2qkBcHs
CAALookup not available with standard resolver
Resolved in 50 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), 663 ms total
PASS
1 redirect(s), 663 ms total
Info::
Single redirect
Got: https://rfc-editor.org → https://www.rfc-editor.org/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 663 ms total
Got: 663 ms

https://rfc-editor.org

59 ms · HTTP/1.1

301

https://www.rfc-editor.org/

603 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://rfc-editor.org30159 msHTTP/1.1cloudflare
2https://www.rfc-editor.org/200603 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:1451, 2606:4700::6812:1551
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700::6812:1451, 2606:4700::6812:1551 Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 3 URLs
PASS
robots.txt present, sitemap with 3 URLs
Info::
robots.txt is present
Got: 240 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 3 entries
Info::
Sitemap index with 3 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 240 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /wp-admin/
Disallow: /authors/
Disallow: /in-notes/authors/
Disallow: /in-notes/rerendered/
Disallow: /rfc/authors/
Disallow: /rfc/rerendered/
Disallow: /rfc/v3test/
Sitemap: https://www.rfc-editor.org/siteindex.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 3 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
rfc-editor.org — via Cloudflare, Inc., 28 years, 4 months old
PASS
rfc-editor.org — via Cloudflare, Inc., 28 years, 4 months old
Info::
Domain registered until May 14, 2031 (5 years, 1 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: Cloudflare, 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.
Domain expiry

1764 days

May 14, 2031

SSL certificate

37 days

Issued by Google Trust Services

Domain age

28 years, 4 months

Registered May 15, 1998

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700::6812:1551

Registrar

Cloudflare, Inc.

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Cloudflare, Inc.
Created May 15, 1998 (28 years, 4 months ago)
Expires May 14, 2031 (5 years, 1 months)
Last Updated February 7, 2026
Name Servers jill.ns.cloudflare.com, ken.ns.cloudflare.com
DNSSEC Enabled
Hosting
IP Address 2606:4700::6812:1551
Data source: rdap (0.6s)

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

Connection waterfall

DNS Lookup 46 ms TCP Connect 16 ms TLS Handshake 22 ms Server Processing 18 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