Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.FRedirect ChainAction5 redirect(s), 4378 ms totalFIX
https://ameba.jp
5 ms · HTTP/1.1
https://www.ameba.jp/
956 ms · HTTP/1.1
https://www.ameba.jp/auth/login?prompt=n...
673 ms · HTTP/1.1
https://auth.user.ameba.jp/connect/autho...
953 ms · HTTP/1.1
https://www.ameba.jp/auth/callback?error...
894 ms · HTTP/1.1
https://www.ameba.jp/loginCheck.do?isAut...
897 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://ameba.jp | 301 | 5 ms | HTTP/1.1 | |
| 2 | https://www.ameba.jp/ | 302 | 956 ms | HTTP/1.1 | |
| 3 | https://www.ameba.jp/auth/login?prompt=n... | 302 | 673 ms | HTTP/1.1 | |
| 4 | https://auth.user.ameba.jp/connect/autho... | 302 | 953 ms | HTTP/1.1 | |
| 5 | https://www.ameba.jp/auth/callback?error... | 302 | 894 ms | HTTP/1.1 | |
| 6 | https://www.ameba.jp/loginCheck.do?isAut... | 302 | 897 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
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
DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BCrawlabilityrobots.txt present, no sitemapREVIEW
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
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
User-agent: Googlebot
Disallow: /?*
Disallow: /apps?*
Disallow: /game?*
Disallow: /api/
Disallow: /auth/
Disallow: /campaign/stamp/
Disallow: /index.do
Disallow: /loginCheck.do
Disallow: /loginCheck
Disallow: /logout
Disallow: /logout.do
Disallow: /logout/
Disallow: /oauth/
Disallow: /settings
Disallow: /settings/
Disallow: /tradelaw/
No sitemap found
Adding a sitemap helps search engines discover your pages.
BTLS Certificate Expiry & Recommendations192 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
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 Records2 A records, 33 ms lookupPASS
| A | 199.232.213.91, 199.232.209.91 |
| AAAA | — |
| CNAME | — |
| NS | ns-115.awsdns-14.com, ns-1836.awsdns-37.co.uk, ns-953.awsdns-55.net, ns-1187.awsdns-20.org |
| MX | 9 smtp-in.csm.ca-pf.org |
| TXT | google-site-verification=fSCrWtW9nTWATvI6R7Kchj6Xz_1Iz7fzVIDZ4FITF_Q google-site-verification=yMcANGCjw849v6OCRkTOrxwdcDPduUQAz3cWP4-ixuE lCkMX44ffUsPSE9hUPmfGyo0JWjVqb google-site-verification=ivH7MJwKzvaaMGT0iX2BuQdeyTZZwdv68LeTfx9Zvio YWI8fk2W7hON4CPm99Lkp3l5qO1EgC google-site-verification=tEpCxWpW6GlLH7IUDVZ5JV6YnyEYvlnu1UlTb4f6uS8 fastly-domain-delegation-tM982%KDILMO-2022-12-12 _ew6yw4b6vfj2yhwt1miun4z719jah5f google-site-verification=K7UYMuat0CKhMGM2tAalW1jOaX7YHcGNyinsuXhq7Gw SPF v=spf1 include:spf-a.ameba.jp include:spf-b.ameba.jp include:spf-f.ameba.jp ~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.
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligenceameba.jp — hosted on FastlyPASS
Unknown
192 days
Issued by Cybertrust Japan Co., Ltd.
Unknown
Status unknown
Protects against DNS spoofing
Fastly
ASN AS54113
199.232.213.91
Registrar unknown