Skip to content
https://asahi.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
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), 1044 ms total
REVIEW
1 redirect(s), 1044 ms total
Info::
Single redirect
Got: https://asahi.com → https://www.asahi.com/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1044 ms total
Got: 1044 ms

https://asahi.com

7 ms · HTTP/1.1

301

https://www.asahi.com/

1036 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://asahi.com3017 msHTTP/1.1AkamaiGHost
2https://www.asahi.com/2001036 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

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.asahi.com/
200https://asahi.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://asahi.com/ → https://www.asahi.com/

Consistent

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

Certificate validity

281
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
  • 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
B
CDN & Delivery
Akamai
REVIEW
Akamai
Info::
Site is served via Akamai CDN
Got: server header
CDN Detected: Akamai
Provider Akamai Evidence server header
A+
DNS Records
1 A records, 87 ms lookup
PASS
1 A records, 87 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 95.100.119.9
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: a1-8.akam.net, a13-67.akam.net, a8-66.akam.net, a26-65.akam.net, a24-64.akam.net, a9-67.akam.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
Info::
DNS resolution time: 87 ms
Got: 87 ms
A95.100.119.9
AAAA—
CNAME—
NSa1-8.akam.net, a13-67.akam.net, a8-66.akam.net, a26-65.akam.net, a24-64.akam.net, a9-67.akam.net
MX
5 mx1.hc198955.iphmx.com
TXT
scsf04ud2j4fg3r6k4q7i61n5s
UT1QRD2OQOHO2E5TJPFRANFNFR
atlassian-domain-verification=ohrq3/7P/gW2J47iXhMcl8otmcHNRpcHPcXaybWaWooX5xaqRr...
MS=F547E41E3C2EAF104E32CBF73F73BB873A66B638
google-site-verification=Uotgq2gHQn13TjlkUBYnSzUuPeNWcY3YSk4hajeifPs
adobe-idp-site-verification=188eaa66-481b-4d2c-b597-7b48f1e4e78e
atlassian-domain-verification=U6Y71Ic4TSCXXnf4Y5seCXu00U6Qihl4kR6Xf6VPSd2fC5RxqV...
google-site-verification=9d7y4c_VMA9CRtFQXc76sRjZWdr1h8EqbJ8Lfa4PtUI
gcxqzzsm94c91c2sh7jptb0vwrn92ygg
MS=ms97639603
SPF v=spf1 include:spf01.asahi.com include:spf02.asahi.com include:spft-v1.apfmail.a...
atlassian-sending-domain-verification=1ea23e66-be1a-4e79-a81e-efb9feaa6dd0
google-site-verification=CMRxn5sb2Pg06cn2vd96PM5x49NFWhatWCxLssbIC2g
seculio-domain-verification-code=f7a843b97c7fd7ed684cef0ad09cd612ee8d164236df2f9...
s7psie6ec1cvpq29659p82trb1
google-site-verification=Zy1eXVKL4P1BqGnAjuIVZp6K31FsDky77X2_kZRRJpU
BSO692QHB47TN5HA2J955LGU75
facebook-domain-verification=kglzpcvp6hq2uec8aburxdrew6f3u7
CAALookup not available with standard resolver
Resolved in 87 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+
Crawlability
robots.txt present, sitemap with 8 URLs
PASS
robots.txt present, sitemap with 8 URLs
Info::
robots.txt is present
Got: 1129 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 8 entries
Info::
Sitemap index with 8 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1129 B Sitemaps referenced 1 User-agents ChatGPT-User, GPTBot, ICC-Crawler, anthropic-ai, Perplexity-ai, AmazonBot, CCBot, Applebot-Extended, omgili, omgilibot, PerplexityBot, Perplexity-User, Bytespider, Googlebot, OAI-SearchBot, ClaudeBot, cohere-ai, *, Google-Extended, Claude-Web, Meta-ExternalAgent, Gensparkbot Blocking No — crawling allowed
User-Agent: *
Disallow: /travel/event/search/
Disallow: /car/index.html
Disallow: /housing/index.html
Disallow: /english/newsfeatures.html
Disallow: /english/business.html
Disallow: /english/cooljapan.html
Disallow: /english/sports.html
Allow: /
Allow: /.well-known/assetlinks.json
Allow: /ads/tu/


User-agent: Googlebot
Disallow: /*klpuid=*

User-agent: CCBot
Disallow: /

User-agent: OAI-SearchBot
Disallow: /

User-agent: ChatGPT-User
Disallow: /

User-agent: GPTBot
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: ICC-Crawler
Disallow: /

User-agent: anthropic-ai
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: Claude-Web
Disallow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: cohere-ai
Disallow: /

User-agent: omgili
Disallow: /

User-agent: omgilibot
Disallow: /

User-agent: PerplexityBot
Disallow: /

User-agent: Perplexity-ai
Disallow: /

User-agent: Perplexity-User
Disallow: /

User-agent: Meta-ExternalAgent
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: Gensparkbot
Disallow: /

User-agent: AmazonBot
Disallow: /

sitemap: https://www.asahi.com/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 8 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
asahi.com — via Japan Registry Services Co., Ltd., 31 years, 1 months old, hosted on Akamai
PASS
asahi.com — via Japan Registry Services Co., Ltd., 31 years, 1 months old, hosted on Akamai
Info::
Domain registered until Jul 28, 2026 (3 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: Japan Registry Services Co., Ltd.
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: Akamai
Got: AS16625
Domain expiry

42 days

July 28, 2026

SSL certificate

281 days

Issued by DigiCert Inc

Domain age

31 years, 1 months

Registered July 29, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Akamai

ASN AS16625

95.100.119.9

Registrar

Japan Registry Services Co., Ltd.

Unlocked 6 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Japan Registry Services Co., Ltd.
Created July 29, 1995 (31 years, 1 months ago)
Expires July 28, 2026 (3 months)
Last Updated July 26, 2025
Name Servers a1-8.akam.net, a13-67.akam.net, a24-64.akam.net, a26-65.akam.net, a8-66.akam.net, a9-67.akam.net
DNSSEC Not enabled
Hosting
IP Address 95.100.119.9
ASN AS16625 (AKAMAI-AS - Akamai Technologies, Inc., US)
Provider Akamai
Data source: rdap (0.3s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more ▾

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

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

Connection waterfall

DNS Lookup 35 ms TCP Connect 1 ms TLS Handshake 4 ms Server Processing 1 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback