Skip to content
https://blog.jp

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
1
REVIEW
5
PASS
3
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
3 PASS 5 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
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more ▾

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

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

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 200 Expected: 301 redirect to HTTPS

www / non-www

404https://www.blog.jp/
200https://blog.jp/

HTTP → HTTPS

200http://blog.jp/

HTTP version does not redirect to HTTPS

B
HTTP Probe Timing
Total 862 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
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.
269 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
272 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
862 ms
Total Time Total request time from DNS lookup through full response.
863 ms

Connection waterfall

DNS Lookup 47 ms TCP Connect 269 ms TLS Handshake 272 ms Server Processing 274 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
58 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • 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, 62 ms lookup
PASS
1 A records, 62 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 147.92.146.242
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1490.awsdns-58.org, ns-815.awsdns-37.net, ns-292.awsdns-36.com, ns-2044.awsdns-63.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: 62 ms
Got: 62 ms
A147.92.146.242
AAAA—
CNAME—
NSns-1490.awsdns-58.org, ns-815.awsdns-37.net, ns-292.awsdns-36.com, ns-2044.awsdns-63.co.uk
MX—
TXT
google-site-verification=L8DXNsXilkkn0D5AINAAPQtxDxdke-EAuDRPBMjZTg0
CAALookup not available with standard resolver
Resolved in 62 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.

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://blog.jp

https://blog.jp

812 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://blog.jp200812 msHTTP/1.1nginx
A+
Domain Intelligence
blog.jp — hosted on LINE LY Corporation, JP
PASS
blog.jp — hosted on LINE LY Corporation, JP
Info::
Hosting: LINE LY Corporation, JP
Got: AS38631
Domain expiry

Unknown

SSL certificate

58 days

Issued by Let's Encrypt

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

LINE LY Corporation, JP

ASN AS38631

147.92.146.242

Registrar

Registrar unknown

Lock status unknown 4 NS records
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Registrar
Name Servers ns-815.awsdns-37.net, ns-292.awsdns-36.com, ns-1490.awsdns-58.org, ns-2044.awsdns-63.co.uk
Hosting
IP Address 147.92.146.242
ASN AS38631 (LINE LY Corporation, JP)
Provider LINE LY Corporation, JP
Data source: whois (1.3s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback