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

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
67
GRADE
D
FIX
3
REVIEW
4
PASS
1
INFO
1
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
1 PASS 4 REVIEW 3 FIX
D
Redirect Chain
Action
2 redirect(s), 2814 ms total
FIX
2 redirect(s), 2814 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
HTTP to HTTPS redirect present
Info::
WWW normalization redirect
Warning::
2-hop chain could be reduced to 1 hop
Redirect directly from https://gnavi.co.jp to https://www.gnavi.co.jp/
Warning::
Redirect overhead: 2814 ms total
Got: 2814 ms

https://gnavi.co.jp

1085 ms · HTTP/1.1

301

http://www.gnavi.co.jp/

585 ms · HTTP/1.1

301

https://www.gnavi.co.jp/

1144 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://gnavi.co.jp3011085 msHTTP/1.1Apache
2http://www.gnavi.co.jp/301585 msHTTP/1.1Apache
3https://www.gnavi.co.jp/2001144 msHTTP/1.1Apache

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

Redirect directly from https://gnavi.co.jp to https://www.gnavi.co.jp/

Why this matters

Redirect chain could be flattened to one hop — server config tweak removes intermediate latency.

Source: web.dev

D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
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
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 301 Expected: 301 redirect to HTTPS

www / non-www

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

Inconsistent — duplicate content risk

HTTP → HTTPS

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

HTTP version does not redirect to HTTPS

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
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 161 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 161 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /*?ndx=t&
Disallow: /*?ndx=t$
Disallow: /*&ndx=t&
Disallow: /*&ndx=t$
Disallow: /*&ndx=t&
Disallow: /*&ndx=t$
Disallow: /okuru/*
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Connection waterfall

DNS Lookup 46 ms TCP Connect 272 ms TLS Handshake 547 ms Server Processing 273 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
140 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

140
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
A+
DNS Records
1 A records, 46 ms lookup
PASS
1 A records, 46 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 103.129.28.29
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-2019.awsdns-60.co.uk, ns-1067.awsdns-05.org, ns-887.awsdns-46.net, ns-110.awsdns-13.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: 46 ms
Got: 46 ms
A103.129.28.29
AAAA—
CNAME—
NSns-2019.awsdns-60.co.uk, ns-1067.awsdns-05.org, ns-887.awsdns-46.net, ns-110.awsdns-13.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 alt4.aspmx.l.google.com
10 alt3.aspmx.l.google.com
TXT
google-site-verification=IbZjA2lQ6fRTKzFigL-Uc2VUjNG3lkPN_EyAosJFolU
SPF v=spf1 ip4:103.129.28.0/22 +ip4:158.201.246.0/27 +ip4:158.201.242.0/27 include:_...
MS=ms90639686
apple-domain-verification=H1eFMVSkarTDU0YL
google-site-verification=NZAhgepkg4UA1u6u8x1WzraD9Qnyf65j9UxPm-KIWrI
jamf-site-verification=SYpV_BfiO4ECMt3UNSQnrg
google-site-verification=GIY8OJ2shK6kgrp-9j37ElJfiHfhl9e4Uuffuk7Onlg
worksmobile-certification=yyuvjns7f99uc3eyln-wajgj1ssrdwwmx-2ugdkwv5g
atlassian-domain-verification=eYVUdiYiYwfE/pb6lcQoJUGap6ClIVRaZrMihCdox0aSb7MKdN...
atlassian-sending-domain-verification=1b4e830e-94fa-4161-a15d-e0a6539db567
xTB6zEMXUnKMxLejt349H8mhNeukXh
CAALookup not available with standard resolver
Resolved in 46 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.

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