Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DRedirect ChainAction2 redirect(s), 1181 ms totalFIX
https://sony.net
723 ms · HTTP/1.1
https://www.sony.net:443/
296 ms · HTTP/1.1
https://www.sony.co.jp/en/
162 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://sony.net | 301 | 723 ms | HTTP/1.1 | awselb/2.0 |
| 2 | https://www.sony.net:443/ | 302 | 296 ms | HTTP/1.1 | Apache |
| 3 | https://www.sony.co.jp/en/ | 200 | 162 ms | HTTP/1.1 | Apache |
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
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
DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
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
BCrawlabilityrobots.txt present, no sitemapREVIEW
A sitemap helps search engines discover and index your pages more efficiently.
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
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
User-agent: Baiduspider
Disallow: /Products/tv/androidtv/
User-agent: BaiduImagespider
Disallow: /Products/tv/androidtv/
User-agent: BaiduMobaider
Disallow: /Products/tv/androidtv/
User-agent: Yeti
Disallow: /Products/tv/androidtv/
User-agent: Googlebot
Disallow: /Products/tv/seeingisbelieving/
User-agent: *
Disallow: /Products/CameraSystem/NVMS/software/exe/hotfix/
User-agent: *
Disallow: /Products/felica/business/tech-support/st_*.html
No sitemap found
Adding a sitemap helps search engines discover your pages.
BTLS Certificate Expiry & Recommendations317 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
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 Records2 A records, 11 ms lookupPASS
| A | 52.6.127.76, 44.218.59.236 |
| AAAA | — |
| CNAME | — |
| NS | a1-166.akam.net, a16-67.akam.net, a24-66.akam.net, a8-65.akam.net, a3-65.akam.net, a13-66.akam.net |
| MX | — |
| TXT | 8lof7e26bg6l7d6sm452ipbtcv 963m3q2rd8eqpvahudc3dhdjdt 202410011422033904D91B9A620C1F5534939443E18E10A7C08D1156AE206241E7D326F91DF9F0 ne2tk84vh088e324qv4unnnuvk ekiugrcjpt1giv7aj7uu1uucnk _9naxs8j4dcaotf02nbfaud2ocsirey2 r99grqshmvqdkg1ovqse3tlsjt _a4brmy7903dekes1yyfgb2sv6bs1zdi _vypn0qm8lejwqnyj2ni6kxnkibilr15 SPF v=spf1 -all |
| CAA | Lookup not available with standard resolver |
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.
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencesony.net — via PSI-Japan, Inc., 26 years, 7 months old, hosted on AWSPASS
548 days
January 11, 2028
317 days
Issued by Amazon
26 years, 7 months
Registered January 11, 2000
Not enabled
Protects against DNS spoofing
AWS
ASN AS14618
44.218.59.236
PSI-Japan, Inc.
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