Skip to content
https://boingboing.net

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
96
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
6 PASS 3 REVIEW
B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 155 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 155 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /cgi-bin
Disallow: /cdn-cgi
Disallow: /wp-json/wp/v2
Disallow: /wp-content/themes/2012/ads/
Disallow: /wp-content/themes/2012/ad_*

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN & Delivery
Cloudflare (BYPASS)
REVIEW
Cloudflare (BYPASS)
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9eff3b34f95af4ff-CDG
Info::
CDN cache status: BYPASS
CDN Detected: Cloudflare
Provider Cloudflare Cache Status BYPASS Evidence cf-ray: 9eff3b34f95af4ff-CDG
A+
DNS Records
2 A records, 32 ms lookup
PASS
2 A records, 32 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.20.34.75, 172.66.163.205
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:10::ac42:a3cd, 2606:4700:10::6814:224b
Info::
2 nameserver(s) configured
Got: ryan.ns.cloudflare.com, lola.ns.cloudflare.com
Info::
5 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: 32 ms
Got: 32 ms
A104.20.34.75, 172.66.163.205
AAAA2606:4700:10::ac42:a3cd, 2606:4700:10::6814:224b
CNAME
NSryan.ns.cloudflare.com, lola.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 alt4.aspmx.l.google.com
10 alt3.aspmx.l.google.com
TXT
facebook-domain-verification=ujgb22qbsx6y12bclz0wv9mtnlccst
google-site-verification=qG5458tEWwgyOlXyyU0Vd7kkj68KqzmrLcpYb3puzCA
SPF v=spf1 ip4:204.11.50.128/28 include:servers.mcsv.net include:amazonses.com inclu...
google-site-verification=rTR1FkvbFSq_2kwZIaJxliNSd-xS4aazQcQRdz8z8j8
google-site-verification=2Z2CdDZoCt3kedjrHnPrbA3HjYnoXwwgy2pjFo552ws
CAALookup not available with standard resolver
Resolved in 32 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://boingboing.net

https://boingboing.net

470 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://boingboing.net200470 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700:10::ac42:a3cd, 2606:4700:10::6814:224b
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:10::ac42:a3cd, 2606:4700:10::6814:224b Connection Reachable (17 ms)
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.boingboing.net/
200https://boingboing.net/

Preferred variant: non-www

HTTP → HTTPS

301http://boingboing.net/ https://boingboing.net/

Consistent

A+
Domain Intelligence
boingboing.net — via Squarespace Domains II LLC, 28 years, 4 months old
PASS
boingboing.net — via Squarespace Domains II LLC, 28 years, 4 months old
Info::
Domain registered until May 5, 2027 (1 years remaining)
Info::
DNSSEC is enabled
Info::
Registrar: Squarespace Domains II 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

323 days

May 5, 2027

SSL certificate

85 days

Issued by Google Trust Services

Domain age

28 years, 4 months

Registered May 6, 1998

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:10::6814:224b

Registrar

Squarespace Domains II LLC

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 Squarespace Domains II LLC
Created May 6, 1998 (28 years, 4 months ago)
Expires May 5, 2027 (1 years)
Last Updated April 20, 2026
Name Servers lola.ns.cloudflare.com, ryan.ns.cloudflare.com
DNSSEC Enabled
Hosting
IP Address 2606:4700:10::6814:224b
Data source: rdap (0.1s)

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 445 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
33 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
17 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.
444 ms
Total Time Total request time from DNS lookup through full response.
445 ms

Connection waterfall

DNS Lookup 33 ms TCP Connect 17 ms TLS Handshake 22 ms Server Processing 372 ms Content Transfer 2 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback