Skip to content
https://mynavi.jp

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
81
GRADE
B
FIX
0
REVIEW
5
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 5 REVIEW
B
Redirect Chain
1 redirect(s), 1465 ms total
REVIEW
1 redirect(s), 1465 ms total
Info::
Single redirect
Got: https://mynavi.jp → https://www.mynavi.jp/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1465 ms total
Got: 1465 ms

https://mynavi.jp

42 ms · HTTP/1.1

301

https://www.mynavi.jp/

1423 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://mynavi.jp30142 msHTTP/1.1Apache
2https://www.mynavi.jp/2001423 msHTTP/1.1Apache

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

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.mynavi.jp/
200https://mynavi.jp/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://mynavi.jp/ → https://mynavi.jp/

Consistent

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

Connection waterfall

DNS Lookup 276 ms TCP Connect 1 ms TLS Handshake 5 ms Server Processing 1.07 s Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
185 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

185
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
4 A records, 258 ms lookup
PASS
4 A records, 258 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 65.8.202.89, 65.8.202.21, 65.8.202.33, 65.8.202.103
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-226.awsdns-28.com, ns-1231.awsdns-25.org, ns-1786.awsdns-31.co.uk, ns-884.awsdns-46.net
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 (258 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 258 ms
A65.8.202.89, 65.8.202.21, 65.8.202.33, 65.8.202.103
AAAA—
CNAME—
NSns-226.awsdns-28.com, ns-1231.awsdns-25.org, ns-1786.awsdns-31.co.uk, ns-884.awsdns-46.net
MX
0 mynavi-jp.mail.protection.outlook.com
TXT
fp1g52m5f2s3daogbhgiliv0pj
pardot826223=e22b179bcd1e1d88f9040df32877d2472fe78ff178bb78a4defda8541352f0d6
MS=ms78238969
zapier-domain-verification-challenge=f4dd7733-14f6-4b47-aa66-a252470ef9f0
SPF v=spf1 ip4:210.190.113.0/24 include:spf-b.mynavi.jp include:_netblocks.google.co...
sending_domain966293=6e366ce79db1719fcf30726863d45b8a0ddd78fc143367dae2c912127c6...
ihurnsq08oqm1kq0j0p73ivj7s
gpf23qfuhluagflg6a76fuuhke
S7mnz2lQ91jDu+kEoUICxeXFewcFtDCxoEULhxJGLDQ=
sending_domain909172=a160018d872c0207a1c2f341193aaa817227f6dee069e7cc5530bb5e2af...
box-domain-verification=437e30101a1180991648322491eccca358188d318ed873ff14565383...
pardot826223=11da39ea2f882ec50f603b4d7912830fdf99314982dafbe9b9f3340914a2a5d4
google-site-verification=Cx23CAksXuk6eKknpbS9GaUX8vnOGcIA4QkJVcJ_BLs
_globalsign-domain-verification=mbV3Qq4yj0wBJydjdhYpvXIyJcoykhZSbe7gDnDtUe
4g0777mtl95b9vd3sfueerv9vg
google-site-verification=LG6ojin994aVke0L4OrxhTxOnkPTSr-PBBb9HcTxRoM
sending_domain826223=774b835f767a315d17fdf2660d6d521a9d6af5f715b5c6627853cf0f8e7...
google-site-verification=swOYyeDdsWUAgD0ossgprRnjkINqDPcNCWtearVOCw0
CAALookup not available with standard resolver
Resolved in 258 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.

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+
Crawlability
robots.txt present, sitemap with 6 URLs
PASS
robots.txt present, sitemap with 6 URLs
Info::
robots.txt is present
Got: 70 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 6 entries
Info::
Sitemap index with 6 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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 70 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *

Allow: /

Disallow: /wp-content/uploads/*/kessan*.pdf
sitemap.xml 200 OK
Type Sitemap Index URLs 6 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
mynavi.jp — hosted on AWS
PASS
mynavi.jp — hosted on AWS
Info::
Hosting: AWS
Got: AS16509
Domain expiry

Unknown

SSL certificate

185 days

Issued by Amazon

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

65.8.202.89

Registrar

Registrar unknown

Lock status unknown 4 NS records
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Registrar
Name Servers ns-884.awsdns-46.net, ns-1231.awsdns-25.org, ns-226.awsdns-28.com, ns-1786.awsdns-31.co.uk
Hosting
IP Address 65.8.202.89
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: whois (1.4s)
A
CDN & Delivery
AWS CloudFront (Miss from cloudfront)
PASS
AWS CloudFront (Miss from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: MAD56-P6)
Got: x-amz-cf-id: E5xl30pvshKs0OmMs7dHUODNTtQ2DfbBSyq3ugbMsDXmvWUTuvfiwQ==
Info::
CDN cache status: Miss from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Miss from cloudfront Evidence x-amz-cf-id: E5xl30pvshKs0OmMs7dHUODNTtQ2DfbBSyq3ugbMsDXmvWUTuvfiwQ==
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback