Skip to content
https://ana.co.jp

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
81
GRADE
B
FIX
0
REVIEW
5
PASS
3
INFO
1
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
3 PASS 5 REVIEW
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 301 Expected: 301 redirect to HTTPS

www / non-www

https://www.ana.co.jp/
200https://ana.co.jp/

HTTP → HTTPS

301http://ana.co.jp/ → http://www.ana.co.jp/

HTTP version does not redirect to HTTPS

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

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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
B
CDN & Delivery
Akamai
REVIEW
Akamai
Info::
Site is served via Akamai CDN
Got: server header
CDN Detected: Akamai
Provider Akamai Evidence server header
A+
DNS Records
1 A records, 30 ms lookup
PASS
1 A records, 30 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 23.10.77.20
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
6 nameserver(s) configured
Got: a1-189.akam.net, a3-67.akam.net, a11-64.akam.net, a22-66.akam.net, a6-64.akam.net, a20-65.akam.net
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: 30 ms
Got: 30 ms
A23.10.77.20
AAAA—
CNAME—
NSa1-189.akam.net, a3-67.akam.net, a11-64.akam.net, a22-66.akam.net, a6-64.akam.net, a20-65.akam.net
MX
10 aspmx.l.google.com
20 alt1.aspmx.l.google.com
TXT
google-site-verification=Wkw7U8k0Ay04LbZ62x_a2EHmKA04HlPJ4ZI9KaLT7AY
SPF v=spf1 +ip4:210.231.106.160/27 include:_spf.google.com +ip4:118.103.91.0/25 +ip4...
globalsign-domain-verification=Oqm08nEtrKt2XnVT-6pX26eg7MD4S5PxR1lTwnVhHi
google-site-verification=aSQiimb24pe-LTjTcDy_hhtIDlGzLYajbksiM_wDdTg
google-site-verification=-btZJqX9jx7kAHfXgzNYsZOZlSp-7D_QPp2LkRxYSFU
google-site-verification=ApJG8UBxOcBYMmVLqJGbvjoi6CwTdhV4MVJOXXERNzo
google-site-verification=UOxolrtdsF40W46GdqKjnKNHDYPXvfjUUILtJV_b3PE
box-domain-verification=c3d2a6df3fb282cfd421eed77637847dbef29ac8b75d843fd8ed3520...
globalsign-domain-verification=514182F4C8C73ED019E229E6C60ACC10
google-site-verification=R-3UKHew-9F5FFvcEe6_4ciCdJEojqDPaqi7htGb91E
globalsign-domain-verification=BVzDfsyz1rn753uGFamwPsNasCeUFcQ7dhjQdb2Qll
CAALookup not available with standard resolver
Resolved in 30 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.

A+
Redirect Chain
0 redirect(s), 6 ms total
PASS
0 redirect(s), 6 ms total

https://ana.co.jp

6 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ana.co.jp3016 msHTTP/1.1AkamaiGHost
A+
HTTP Probe Timing
Total 39 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
32 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
5 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
39 ms
Total Time Total request time from DNS lookup through full response.
39 ms

Connection waterfall

DNS Lookup 32 ms TCP Connect 1 ms TLS Handshake 5 ms Server Processing 1 ms Content Transfer 0 ms
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