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

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
80
GRADE
B
FIX
1
REVIEW
5
PASS
2
INFO
1
Probed from Sao Paulo, Brazil
301 Moved Permanently
Checks
9
2 PASS 5 REVIEW 1 FIX
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.

B
Redirect Chain
0 redirect(s), 1172 ms total
REVIEW
0 redirect(s), 1172 ms total
Warning::
Redirect overhead: 1172 ms total
Got: 1172 ms

https://rakuten.co.jp

1172 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://rakuten.co.jp3011172 msHTTP/1.1Apache
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
HTTP Probe Timing
Total 1169 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
303 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
288 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
290 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.17 s
Total Time Total request time from DNS lookup through full response.
1.17 s

Connection waterfall

DNS Lookup 303 ms TCP Connect 288 ms TLS Handshake 290 ms Server Processing 289 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
92 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

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 Records
1 A records, 318 ms lookup
PASS
1 A records, 318 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 133.237.182.225
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: ns02.rakuten.ad.jp, ns02.rakuten.co.jp, ns06.rakuten.co.jp, ns01.rakuten.co.jp, ns03.rakuten.co.jp, ns01.rakuten.ad.jp
Info::
1 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
Warning::
DNS resolution is slow (318 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 318 ms
A133.237.182.225
AAAA—
CNAME—
NSns02.rakuten.ad.jp, ns02.rakuten.co.jp, ns06.rakuten.co.jp, ns01.rakuten.co.jp, ns03.rakuten.co.jp, ns01.rakuten.ad.jp
MX
0 rakuten-co-jp.mail.protection.outlook.com
TXT
SPF v=spf1 include:spf01.rakuten.co.jp include:spf02.rakuten.co.jp ~all
6c62zsshdj6rx8rchn06f5996q5449zl
google-site-verification=jEVlUFe4ObKQwKXSMwI8eHSxbSurL8iVFJjjTgDWU0k
apple-domain-verification=UeLEhRNLNKOofIvN
jjh5xgsjhfkfv2p1c4pnw695wt2d1b6m
_b6ls5cifmj3tlp051i6dr0ipvvl1d6i
google-site-verification=jfLP2TbPbqJSVvxptWAbrLvNNVLjpww-_Ra0KyD65EQ
google-site-verification=SqqGXNFfgMep3bc91Z3f7RLBgYf-H-Fy5bF184JY56k
google-site-verification=MMXQSgt7rmd8Qi1qW8vK1usn1zCT5V-d-I7UUr5gCEQ
google-site-verification=HB8QvSCuaOINaXr1P_gtW8S9ijT9a13u-YAiBMPBokg
_ab59puqfo49ja7egf36yhx1ceczcjt0
dk81fmlb8ts78g53lrq4dv43z6dprl6x
crk3qs7nrs2gw6ns59glnk3kpg34yb96
pardot1107312=6d02f8a191b3fa3cb2a63a0f8896b6b178977a6f295ef9bce9c81c2e76bbd512
42n2gr6qxm8zrk7zn6353mc1kh76xtn0
_a23mdvjjysoqfsda5syosc3y3g8dixv
CAALookup not available with standard resolver
Resolved in 318 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.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

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

HTTP → HTTPS

301http://rakuten.co.jp/ → https://www.rakuten.co.jp/

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