Skip to content
https://b.hatena.ne.jp

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
4
INFO
1
Probed from Madrid, Spain
200 OK
Checks
9
4 PASS 3 REVIEW 1 FIX
D
HTTP Probe Timing
Action
Total 2768 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
FIX
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
29 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.
19 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
2.34 s
Total Time Total request time from DNS lookup through full response.
2.77 s

Connection waterfall

DNS Lookup 29 ms TCP Connect 16 ms TLS Handshake 19 ms Server Processing 2.28 s Content Transfer 429 ms
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: 875 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 875 B Sitemaps referenced 0 User-agents *, Slurp, Googlebot, Mediapartners-Google Blocking No — crawling allowed
User-agent: *
Disallow: /api/entry/http
Disallow: /api/entry/info
Disallow: /api/internal/bookmarks/shares_and_clicks
Disallow: /api/internal/cambridge/user
Disallow: /api/related_entries/
Disallow: /api/users/*/bookmarks
Disallow: /entry/button/
Disallow: /entry.count
Disallow: /entry/image/
Disallow: /entry/jsonlite
Disallow: /guide/bbutton?url=*
Disallow: /-/webextension/*
Crawl-delay: 5

User-agent: Slurp
Disallow: /

User-agent: Googlebot
User-agent: Mediapartners-Google
Disallow: /api/entry/http
Disallow: /api/entry/info
Disallow: /api/internal/bookmarks/shares_and_clicks
Disallow: /api/internal/cambridge/user
Disallow: /api/related_entries/
Disallow: /api/users/*/bookmarks
Disallow: /entry/button/
Disallow: /entry.count
Disallow: /entry/*/comment/*
Disallow: /entry/image/
Disallow: /entry/jsonlite
Disallow: /guide/bbutton?url=*
Disallow: /-/webextension/*
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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
4 A records, 29 ms lookup
PASS
4 A records, 29 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 143.204.194.33, 143.204.194.64, 143.204.194.60, 143.204.194.96
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-342.awsdns-42.com, ns-745.awsdns-29.net, ns-1269.awsdns-30.org, ns-1803.awsdns-33.co.uk
Info::
No MX records — email not configured via DNS
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: 29 ms
Got: 29 ms
A143.204.194.33, 143.204.194.64, 143.204.194.60, 143.204.194.96
AAAA—
CNAME—
NSns-342.awsdns-42.com, ns-745.awsdns-29.net, ns-1269.awsdns-30.org, ns-1803.awsdns-33.co.uk
MX—
TXT
google-site-verification=OiwrDLnHFIxHhqT-KhGTVHL1NyKyNE0ijZB2rNJAqeg
google-site-verification=8LgDASN6vMoQRh8-pzj1uZ6YdMRwEVLmkC6u1RsoMh4
CAALookup not available with standard resolver
Resolved in 29 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://b.hatena.ne.jp

https://b.hatena.ne.jp

60 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://b.hatena.ne.jp20060 msHTTP/1.1nginx
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

https://www.b.hatena.ne.jp/
200https://b.hatena.ne.jp/

HTTP → HTTPS

301http://b.hatena.ne.jp/ → https://b.hatena.ne.jp/

Consistent

A
CDN & Delivery
AWS CloudFront (Miss from cloudfront)
PASS
AWS CloudFront (Miss from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: CDG54-P1)
Got: x-amz-cf-id: zwi2nDCVUIAMhbGaHK73VEJ59lsVZ4wBuk0WGPk0YiGjPJnCpgb8qA==
Info::
CDN cache status: Miss from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Miss from cloudfront Evidence x-amz-cf-id: zwi2nDCVUIAMhbGaHK73VEJ59lsVZ4wBuk0WGPk0YiGjPJnCpgb8qA==
Domain Intelligence
Domain intelligence data not available
INFO
Domain intelligence data not available

RDAP and WHOIS lookup both failed

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback