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

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
70
GRADE
C
FIX
2
REVIEW
4
PASS
2
INFO
1
Probed from Santa Clara, United States
301 Moved Permanently
Checks
9
2 PASS 4 REVIEW 2 FIX
F
IPv6 Readiness
Action
IPv6 records exist but unreachable
FIX
IPv6 records exist but unreachable
Warning::
IPv6 DNS records exist but server is not reachable
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Got: 2600:9000:a516:b513:4d6:f3c4:677e:66c3, 2600:9000:a609:633:3b83:3b93:7969:130a
Info::
IPv6 connection error
Got: dial tcp6 [2600:9000:a516:b513:4d6:f3c4:677e:66c3]:443: connect: network is unreachable
IPv6 Misconfigured
AAAA Records 2600:9000:a516:b513:4d6:f3c4:677e:66c3, 2600:9000:a609:633:3b83:3b93:7969:130a Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more ▾

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

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
1 redirect(s), 1279 ms total
REVIEW
1 redirect(s), 1279 ms total
Info::
Single redirect
Got: https://ocn.ne.jp → https://www.ocn.ne.jp:443/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1279 ms total
Got: 1279 ms

https://ocn.ne.jp

449 ms · HTTP/1.1

301

https://www.ocn.ne.jp:443/

830 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ocn.ne.jp301449 msHTTP/1.1awselb/2.0
2https://www.ocn.ne.jp:443/200830 msHTTP/1.1Apache

See the visual redirect chain in the HTTP Probe tab →

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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

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

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://ocn.ne.jp/ → https://www.ocn.ne.jp:443/

Consistent

B
TLS Certificate Expiry & Recommendations
284 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

284
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
2 A records, 124 ms lookup
PASS
2 A records, 124 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 166.117.45.22, 166.117.182.151
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2600:9000:a516:b513:4d6:f3c4:677e:66c3, 2600:9000:a609:633:3b83:3b93:7969:130a
Info::
2 nameserver(s) configured
Got: ns2.ocn.ad.jp, ns1.ocn.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
Info::
DNS resolution time: 124 ms
Got: 124 ms
A166.117.45.22, 166.117.182.151
AAAA2600:9000:a516:b513:4d6:f3c4:677e:66c3, 2600:9000:a609:633:3b83:3b93:7969:130a
CNAME—
NSns2.ocn.ad.jp, ns1.ocn.ad.jp
MX
10 mw2prrw31p.bizmw.com
TXT
spf2.0/mfrom,pra -all
SPF v=spf1 -all
_b3myaafzngh64e3a5lsksz7s94rop0w
ga6esjqhf1q9evpd7j38amplb9
google-site-verification=n4lLeQpESt0f-02722buq0I-42N8Z0Yu8_22ybcQtZs
CAALookup not available with standard resolver
Resolved in 124 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
HTTP Probe Timing
Total 455 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
124 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
4 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
218 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
455 ms
Total Time Total request time from DNS lookup through full response.
456 ms

Connection waterfall

DNS Lookup 124 ms TCP Connect 4 ms TLS Handshake 218 ms Server Processing 110 ms Content Transfer 0 ms
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