Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DURL VariantsActionwww/non-www, trailing slash, HTTP→HTTPSFIX
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
HTTP version does not redirect to HTTPS
DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BTLS Certificate Expiry & Recommendations157 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
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
A+DNS Records1 A records, 80 ms lookupPASS
| A | 175.129.0.108 |
| AAAA | 2001:268:fa03:500:175:129:0:108 |
| CNAME | — |
| NS | dns103.kddi.ne.jp, dns104.kddi.ne.jp, dnsa01.kddi.ne.jp, dnsa02.kddi.ne.jp |
| MX | 10 mx13.au.com 10 mx22.au.com 10 mx23.au.com 10 mx11.au.com 10 mx21.au.com 10 mx24.au.com 10 mx14.au.com 10 mx12.au.com |
| TXT | SPF v=spf1 include:spf-msg.au.com include:spf-nao.ezweb.ne.jp include:spf-az.ezweb.n... _q4bt6hn4w4if9b8ulnocf859fx8yhjj c0lq1l6y7xsj3mk71bg4vdrt1w68s0s8 google-site-verification=tWk10LY-wUsS3rhdu-DKdHDIG08gcEPQaCQJRlU91wg facebook-domain-verification=mroapooxpo8mbwuajmzynp8ni6g32m |
| 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.
ARedirect Chain1 redirect(s), 571 ms totalPASS
https://au.com
397 ms · HTTP/1.0
https://www.au.com/
174 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://au.com | 302 | 397 ms | HTTP/1.0 | BigIP |
| 2 | https://www.au.com/ | 200 | 174 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
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
A+IPv6 ReadinessIPv6 reachable (69 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 5475 URLsPASS
User-Agent:*
Disallow:/cs/pay342/
Disallow:/cs/pay447/
Disallow:/cs/pay457/
Disallow:/support/faq/included/
Disallow:/*jcr:content*
Disallow:/*_jcr_content*
Disallow:/content/dam/au-com/mobile/gimon/disallow/pdf/*.pdf$
Sitemap:https://www.au.com/sitemap.xml
A+Domain Intelligenceau.com — via PSI-Japan, Inc., 28 years, 5 months oldPASS
52 days
August 7, 2026
157 days
Issued by GlobalSign nv-sa
28 years, 5 months
Registered April 3, 1998
Not enabled
Protects against DNS spoofing
Unknown
2001:268:fa03:500:175:129:0:108
PSI-Japan, Inc.
Expiry timeline
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
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