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

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
74
GRADE
C
FIX
2
REVIEW
4
PASS
2
INFO
1
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
2 PASS 4 REVIEW 2 FIX
F
Redirect Chain
Action
3 redirect(s), 1724 ms total
FIX
3 redirect(s), 1724 ms total
Warning::
3 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1724 ms total
Got: 1724 ms
Info::
Cross-domain redirect detected

https://nintendo.co.jp

892 ms · HTTP/1.1

301

https://www.nintendo.co.jp:443/

128 ms · HTTP/1.1

301

https://www.nintendo.co.jp/index.html

2 ms · HTTP/1.1

301

https://www.nintendo.com/jp/index.html

703 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://nintendo.co.jp301892 msHTTP/1.1awselb/2.0
2https://www.nintendo.co.jp:443/301128 msHTTP/1.1AkamaiGHost
3https://www.nintendo.co.jp/index.html3012 msHTTP/1.1
4https://www.nintendo.com/jp/index.html200703 msHTTP/1.1AmazonS3

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

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: 1046 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 1046 B Sitemaps referenced 0 User-agents *, Kangaroo Bot, Omgilibot, PetalBot, Timpibot, Bytespider, Diffbot, Applebot-Extended, Nutch, PanguBot, FacebookBot, FriendlyCrawler, Claude-Web, Claudebot, cohere-ai, cohere-training-data-crawler, Omgili, Webzio-Extended, AI2Bot, AI2Bot-Dolma, CCBot, ICC-Crawler, GPTBot, Google-Extended, Meta-ExternalAgent Blocking No — crawling allowed
#
User-agent: *
disallow: /status
disallow: /cgi-bin/
disallow: /n01/n64/software/nus_p_nk4j/gallery/
disallow: /n01/n64/software/nus_p_nalj/smash/

# Blocked Bots
User-agent: Kangaroo Bot
Disallow: /

User-agent: Nutch
Disallow: /

User-agent: Omgili
Disallow: /

User-agent: Omgilibot
Disallow: /

User-agent: PanguBot
Disallow: /

User-agent: PetalBot
Disallow: /

User-agent: Timpibot
Disallow: /

User-agent: Webzio-Extended
Disallow: /

User-agent: AI2Bot
Disallow: /

User-agent: AI2Bot-Dolma
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: Diffbot
Disallow: /

User-agent: FacebookBot
Disallow: /

User-agent: FriendlyCrawler
Disallow: /

User-agent: ICC-Crawler
Disallow: /

User-agent: GPTBot
Disallow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: Claude-Web
Disallow: /

User-agent: Claudebot
Disallow: /

User-agent: cohere-ai
Disallow: /

User-agent: cohere-training-data-crawler
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: Meta-ExternalAgent
Disallow: /
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
HTTP Probe Timing
Total 1146 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
270 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.
656 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.15 s
Total Time Total request time from DNS lookup through full response.
1.15 s

Connection waterfall

DNS Lookup 270 ms TCP Connect 1 ms TLS Handshake 656 ms Server Processing 219 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
116 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

116
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
2 A records, 55 ms lookup
PASS
2 A records, 55 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 76.223.57.182, 13.248.184.86
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1938.awsdns-50.co.uk, ns-1222.awsdns-24.org, ns-19.awsdns-02.com, ns-742.awsdns-28.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: 55 ms
Got: 55 ms
A76.223.57.182, 13.248.184.86
AAAA—
CNAME—
NSns-1938.awsdns-50.co.uk, ns-1222.awsdns-24.org, ns-19.awsdns-02.com, ns-742.awsdns-28.net
MX
10 mxb-0039de01.gslb.pphosted.com
10 mxa-0039de01.gslb.pphosted.com
TXT
hpe-greenlake-domain-verification=4f6733627049375035647a64534546414c4373735a716c...
work-accounts-domain-verification=eRWIdeFXxgZHuLNTXIt49By7vQfRv0
autodesk-domain-verification=_y-H0jxHOVe0ZiV1NN4y
atlassian-domain-verification=WF623cprMdhlA/kW19/vbZnbfjuZBNy0bhcsGAbLh2Zp44D/au...
notion-domain-verification=9FfnZxkhhgkQtIu4Bky6M4O4YdE9XRhv8ztMj61BO7Y
docusign=8bae5b87-e1b7-4a60-9dce-8eda01e271d5
asv=d66f71b2b2395e9f5079cd35105052f7
google-site-verification=b54lCzSswRrTgAEeAVHa-FgL1XPyBajbTbZ-xOsPmTo
jamf-site-verification=u4XecBBibLG7gb9mCrB6Pg
adobe-idp-site-verification=e520c320-efba-4a1f-b1d8-15e71f1f9230
MS=ms41030733
apple-domain-verification=QU2l91UuVdQA0I1pKv6axF-ftmdc8WWX-EM_uhXJyvU
SPF v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all
CAALookup not available with standard resolver
Resolved in 55 ms

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+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.nintendo.co.jp/
200https://nintendo.co.jp/

Preferred variant: non-www

HTTP → HTTPS

301http://nintendo.co.jp/ → https://www.nintendo.co.jp:443/

Consistent

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