Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BCrawlabilityno robots.txt, no sitemapREVIEW
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
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.
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
No robots.txt found
This is fine for most sites — a missing robots.txt allows all crawling by default.
No sitemap found
Adding a sitemap helps search engines discover your pages.
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations157 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Add includeSubDomains to the HSTS directive
- Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
- 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
BCDN & DeliveryAWS CloudFront (FunctionGeneratedResponse from cloudfront)REVIEW
A+DNS Records4 A records, 63 ms lookupPASS
| A | 52.222.132.11, 52.222.132.53, 52.222.132.14, 52.222.132.77 |
| AAAA | 2600:9000:201a:1a00:1f:48e3:7780:93a1, 2600:9000:201a:a600:1f:48e3:7780:93a1, 2600:9000:201a:3800:1f:48e3:7780:93a1, 2600:9000:201a:2400:1f:48e3:7780:93a1, 2600:9000:201a:e400:1f:48e3:7780:93a1, 2600:9000:201a:ec00:1f:48e3:7780:93a1, 2600:9000:201a:3c00:1f:48e3:7780:93a1, 2600:9000:201a:d600:1f:48e3:7780:93a1 |
| CNAME | — |
| NS | ns-1763.awsdns-28.co.uk, ns-773.awsdns-32.net, ns-469.awsdns-58.com, ns-1076.awsdns-06.org |
| MX | 0 kantei-go-jp.mail.protection.outlook.com |
| TXT | MS=ms71830828 MS=4EDE4CC0C8C2ECC3468C6740E22686CAD3A029B9 SPF v=spf1 include:spf.securemx.jp. include:spf.protection.outlook.com -all |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
ARedirect Chain1 redirect(s), 830 ms totalPASS
https://kantei.go.jp
18 ms · HTTP/1.1
https://www.kantei.go.jp/
812 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://kantei.go.jp | 302 | 18 ms | HTTP/1.1 | none |
| 2 | https://www.kantei.go.jp/ | 200 | 812 ms | HTTP/1.1 | none |
See the visual redirect chain in the HTTP Probe tab →
If permanent, use 301 instead.
302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.
Learn more ▾ ▴
Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).
Source: Google Search Central
A+IPv6 ReadinessIPv6 reachable (1 ms)PASS
A+HTTP Probe TimingTotal 74 ms — DNS, TCP, TLS, TTFB, content transfer breakdownPASS
Connection waterfall
Domain IntelligenceDomain intelligence data not availableINFO
RDAP and WHOIS lookup both failed