Skip to content
https://sakura.ne.jp

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
79
GRADE
C
FIX
1
REVIEW
5
PASS
2
INFO
1
Probed from Madrid, Spain
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.

C
DNS Records
Action
1 A records, 263 ms lookup
REVIEW
1 A records, 263 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 163.43.179.80
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: site-113401987442.gslb12.sakura.ne.jp
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Warning::
DNS resolution is slow (263 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 263 ms
A163.43.179.80
AAAA—
CNAMEsite-113401987442.gslb12.sakura.ne.jp
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 263 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

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

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

B
Redirect Chain
1 redirect(s), 2566 ms total
REVIEW
1 redirect(s), 2566 ms total
Info::
Single redirect
Got: https://www.sakura.ne.jp → https://rs.sakura.ad.jp/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 2566 ms total
Got: 2566 ms
Info::
Cross-domain redirect detected

https://www.sakura.ne.jp

1042 ms · HTTP/1.1

301

https://rs.sakura.ad.jp/

1524 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.sakura.ne.jp3011042 msHTTP/1.1nginx
2https://rs.sakura.ad.jp/2001524 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

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

C
HTTP Probe Timing
Action
Total 1746 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
724 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
255 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
511 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.75 s
Total Time Total request time from DNS lookup through full response.
1.75 s

Connection waterfall

DNS Lookup 724 ms TCP Connect 255 ms TLS Handshake 511 ms Server Processing 255 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
161 days until leaf cert expires — 6 issues to address
REVIEW

Certificate validity

161
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
  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • 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
A+
Crawlability
robots.txt present, sitemap with 55 URLs
PASS
robots.txt present, sitemap with 55 URLs
Info::
robots.txt is present
Got: 222 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 55 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 222 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /column/wp-admin/
Allow: /column/wp-admin/admin-ajax.php

User-agent: *
Disallow: /*?wordfence_lh=1

Sitemap: https://rs.sakura.ad.jp/sitemap.xml
Sitemap: https://rs.sakura.ad.jp/column/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 55 entries Valid XML Yes
Sample URLs:
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

200https://www.sakura.ne.jp/
https://sakura.ne.jp/

HTTP → HTTPS

301http://www.sakura.ne.jp/ → https://www.sakura.ne.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