Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.FRedirect ChainAction3 redirect(s), 1878 ms totalFIX
https://nippon.com
722 ms · HTTP/1.1
https://www.nippon.com/
842 ms · HTTP/1.1
http://www.nippon.com/ja/
34 ms · HTTP/1.1
https://www.nippon.com/ja/
281 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://nippon.com | 302 | 722 ms | HTTP/1.1 | Apache/2.4.56 () |
| 2 | https://www.nippon.com/ | 301 | 842 ms | HTTP/1.1 | Apache/2.4.56 () |
| 3 | http://www.nippon.com/ja/ | 301 | 34 ms | HTTP/1.1 | CloudFront |
| 4 | https://www.nippon.com/ja/ | 200 | 281 ms | HTTP/1.1 | Apache/2.4.56 () |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
Redirect directly from https://nippon.com to https://www.nippon.com/ja/
Redirect chain could be flattened to one hop — server config tweak removes intermediate latency.
Source: web.dev
If permanent, use 301 instead.
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
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BHTTP Probe TimingTotal 1006 ms — DNS, TCP, TLS, TTFB, content transfer breakdownREVIEW
Connection waterfall
BTLS Certificate Expiry & Recommendations221 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- 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
ADNS Records1 A records, 273 ms lookupPASS
| A | 18.65.185.84 |
| AAAA | — |
| CNAME | — |
| NS | 02.dnsv.jp, 04.dnsv.jp, 03.dnsv.jp, 01.dnsv.jp |
| MX | 1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com |
| TXT | apple-domain-verification=rrN7HXozHRDHJpO6 google-site-verification=Zn4FwzEzfhzqhrvCKYoGqajqd1cm_a4zhPRyekeq6ss SPF v=spf1 include:9foceyges9.powerspf.com -all |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
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.
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.
DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.
Source: DNS performance benchmarks
A+Crawlabilityrobots.txt present, sitemap with 6 URLsPASS
User-agent: *
Disallow: */webcheck1/
Disallow: */webcheck2/
Disallow: /simple.html$
Disallow: /api/
User-agent: ia_archiver
Disallow: /
User-Agent: Googlebot
Allow: */ncommon/
Disallow: */webcheck1/
Disallow: */webcheck2/
Disallow: /simple.html$
Disallow: /api/
User-Agent: Twitterbot
Allow: */ncommon/
Allow: /*.js$
Allow: /*.css$
Disallow: */webcheck1/
Disallow: */webcheck2/
Disallow: /simple.html$
Disallow: /api/
User-Agent: Googlebot-News
Allow: */ncommon/
Allow: /*.js$
Allow: /*.css$
Disallow: */webcheck1/
Disallow: */webcheck2/
Disallow: /simple.html$
Disallow: /api/
User-Agent: Baiduspider
Disallow: */webcheck1/
Disallow: */webcheck2/
Disallow: /simple.html$
Disallow: /api/
Sitemap: https://www.nippon.com/ja/sitemap.xml
Sitemap: https://www.nippon.com/en/sitemap.xml
Sitemap: https://www.nippon.com/fr/sitemap.xml
Sitemap: https://www.nippon.com/cn/sitemap.xml
Sitemap: https://www.nippon.com/hk/sitemap.xml
Sitemap: https://www.nippon.com/ar/sitemap.xml
Sitemap: https://www.nippon.com/es/sitemap.xml
Sitemap: https://www.nippon.com/ru/sitemap.xml
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencenippon.com — via GMO Internet Group, Inc. d/b/a Onamae.com, 34 years, 8 months old, hosted on AWSPASS
244 days
February 15, 2027
221 days
Issued by Nijimo, Inc.
34 years, 8 months
Registered February 14, 1992
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
18.65.185.84
GMO Internet Group, Inc. d/b/a Onamae.com
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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.
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