Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DRedirect ChainAction2 redirect(s), 2970 ms totalFIX
https://global.fujitsu
443 ms · HTTP/1.1
https://www.fujitsu.com/global/about/our...
116 ms · HTTP/1.1
https://global.fujitsu/en-global/about/c...
2411 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://global.fujitsu | 302 | 443 ms | HTTP/1.1 | |
| 2 | https://www.fujitsu.com/global/about/our... | 301 | 116 ms | HTTP/1.1 | AkamaiGHost |
| 3 | https://global.fujitsu/en-global/about/c... | 200 | 2411 ms | HTTP/1.1 |
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
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, sitemap with 2454 URLsREVIEW
Search engines may not be able to parse the sitemap. Fix XML validation errors.
An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.
Learn more ▾ ▴
Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.
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
BTLS Certificate Expiry & Recommendations168 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
BCDN & DeliveryAzure CDN (CONFIG_NOCACHE)REVIEW
A+DNS Records1 A records, 8 ms lookupPASS
| A | 150.171.109.148 |
| AAAA | — |
| CNAME | — |
| NS | ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info |
| MX | — |
| TXT | _globalsign-domain-verification=UvdfeOX-dgX-2xd0puqQ4SQDmRDY1f2XUq8AAvEK-P SPF v=spf1 -all pardot951842=3892c3b3a3c9ccdb2822d63e6015e6012497b35bdff3ea7aa9d29abc65e9e4ed pardot956762=49930f0c95719e45b0e6f7bf4dc566830820d16a0142e5c6ae9f7763ff76569b pardot956762=d5d5db09e7fefb0c089eea362ed63b67a40df7658405fa11ede90132c137547b pardot986791=b523bd8a514421790e1c83ee9dced36e41b3e0a1e6868875c6280ddf02f403ca pardot995992=7a034ae3f41d307004dda6937cb34908d52ee85dccd2fd3417451b89a8412a36 pardot995992=d62b5949ab260b0442d480a0f3c50d07bab2b64ff531343cbc42ff32547e8a21 pardot957262=1cae0ab92817001399b96b091fe38538e7f6a39dd58d659d54205ab5aae095f4 _globalsign-domain-verification=-_7KwwTiUHdsmGFqCi6kKIEo-eodmgJMqyyiIb9GvR _mq43qibrr63b82ocgd1muawgkgxx09j _globalsign-domain-verification=VomcpSSplnyQ2UXD5VkSO90qTEetw24AGmsfLeteMw _globalsign-domain-verification=QA5irEex54IpTeS-r9zcsdgsGd54juMIvMgPBBdJJ5 |
| 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.
AURL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
HTTP → HTTPS
Use 301 (permanent) instead of 302 (temporary)
A+Domain Intelligenceglobal.fujitsu — via GMO BRAND SECURITY Inc., 3 years, 2 months old, hosted on Microsoft AzurePASS
267 days
March 7, 2027
168 days
Issued by GlobalSign nv-sa
3 years, 2 months
Registered March 7, 2023
Not enabled
Protects against DNS spoofing
Microsoft Azure
ASN AS8075
150.171.109.145
GMO BRAND SECURITY 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