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

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
81
GRADE
B
FIX
1
REVIEW
4
PASS
3
INFO
1
Probed from Madrid, Spain
302 Found
Checks
9
3 PASS 4 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
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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 0 Expected: 301 redirect to HTTPS

www / non-www

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

HTTP → HTTPS

http://jal.co.jp/

HTTP version does not redirect to HTTPS

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

Certificate validity

339
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, 56 ms lookup
PASS
1 A records, 56 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 18.178.219.162
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns019-ippc778d0s9d9quh.i.d-53.jp, ns019-ippc778d0s9d9quh.i.d-53.info, ns019-ippc778d0s9d9quh.i.d-53.net
Info::
5 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: 56 ms
Got: 56 ms
A18.178.219.162
AAAA—
CNAME—
NSns019-ippc778d0s9d9quh.i.d-53.jp, ns019-ippc778d0s9d9quh.i.d-53.info, ns019-ippc778d0s9d9quh.i.d-53.net
MX
1 aspmx.l.google.com
10 alt2.aspmx.l.google.com
10 alt1.aspmx.l.google.com
20 alt4.aspmx.l.google.com
20 alt3.aspmx.l.google.com
TXT
google-site-verification=-aDG-L__l9F1XsWmUTXcoHp05mWhhfcbGkPi0bT9qYs
google-site-verification=_Drief9KrSwo9Ct8K5g01DkDH6w9WvNUeSrXNxEtzTA
google-site-verification=rRfodkQxQk2wAkKY7D1q5fR5K7b-n2RwFKdoDmu7zMw
google-site-verification=ap0gZxMczl6sDEUqipYYDO2u2-i81OnVKAXi-3IDwa4
v=verifydomain MS=ms88274924
google-site-verification=TwpQX5iS_zhNDi9MZNOOqDhZ1Ej7A8M1EcHjiNu6jGQ
SPF v=spf1 +ip4:202.219.37.2 +ip4:163.211.251.0/24 +ip4:163.211.252.0/24 +ip4:163.21...
google-site-verification=yhoOj0H0fH2H0nXI8wiklB9wc6qwuzLLoilidfLP-xs
google-site-verification=tSppp1YPvoO4kygjYxuJj1N8aO4nmBfvG49lQB3iGSA
google-site-verification=PJbIK19yn3KDob8Q6A71wNKGltXvVjHY0Y9U1Eby9d8
fastly-domain-delegation-H7s9jh78HnIUoImziop9k-20240215
google-site-verification=DpMMzCjEM4CXmLjaCmInOsmSEKeSstVty_DfVrAf774
google-site-verification=QTuZwFHnecpX3OO3FD6qPSqYfXvMSJoORRIPq2rCago
CAALookup not available with standard resolver
Resolved in 56 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.

A+
Redirect Chain
0 redirect(s), 690 ms total
PASS
0 redirect(s), 690 ms total
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://jal.co.jp
Info::
Redirect overhead: 690 ms total
Got: 690 ms

https://jal.co.jp

690 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://jal.co.jp302690 msHTTP/1.1

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

A
HTTP Probe Timing
Total 717 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
36 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
225 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
226 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
718 ms
Total Time Total request time from DNS lookup through full response.
718 ms

Connection waterfall

DNS Lookup 36 ms TCP Connect 225 ms TLS Handshake 226 ms Server Processing 231 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