Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BRedirect Chain1 redirect(s), 1027 ms totalREVIEW
https://oaic.gov.au
304 ms · HTTP/1.1
https://www.oaic.gov.au/
722 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://oaic.gov.au | 302 | 304 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.oaic.gov.au/ | 200 | 722 ms | HTTP/1.1 | cloudflare |
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
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
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations64 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
ADNS Records1 A records, 213 ms lookupPASS
| A | 43.245.41.125 |
| AAAA | — |
| CNAME | — |
| NS | ext-dns1.ssc.gov.au, ext-dns2.ssc.gov.au |
| MX | 10 mail1.employment.gov.au 10 mail2.employment.gov.au |
| TXT | MS=ms23138970 have-i-been-pwned-verification=303f92c143992c055cce870d122307fd q3078k4vrdqkbhy40h64j7ycx3bm5j5k MS=ms63156302 appspace-domain-verification=d4338b639a678e788fa3fa3712005900846ba44206e590da5e2... jqxwh5g407qghd4rb7src44dsmx8b6sy 17nr100vvtm9lk8jncz14j6b2d2ytkvv apple-domain-verification=s85wQ5d2gJ5Zlkj2 pw2dflrl87d46gnrwj6ld2t56mnm9bkn adobe-idp-site-verification=6a79361774d6a4962dbf1d86650a9617c265ab5a828d8a300cce... SPF v=spf1 mx include:spf.protection.outlook.com include:spf.dynect.net include:mail... 0nly7ScDm/nQcwbCXh1hIDeYn0tqlqZgbE0Hq/MY/gkIuHPDEq5jmI8gEzeSgAsIvSiUVzcRUWPEoWct... |
| 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 9 URLsPASS
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
# Disallow some matrix defaults
User-agent: *
Disallow: /*?sq_content_src=
Disallow: /*_recache
Disallow: /*_edit
Disallow: /*_admin
Disallow: /*_login
Disallow: /*_performance
Disallow: /*_design
Disallow: /*?*
Disallow: /*_result_page=*
Disallow: /*start_rank=*
Disallow: /*_media
Disallow: /search
- https://www.oaic.gov.au
- https://www.oaic.gov.au/about-the-OAIC/our-corporate-information/memorandums-of-understanding/current-memorandums-of-understanding/national-facial-biometric-matching-capability/mou-in-relation-to-national-facial-biometric-matching-capability
- https://www.oaic.gov.au/about-the-OAIC/our-corporate-information/memorandums-of-understanding/current-memorandums-of-understanding/consumer-data-right/mou-with-the-australian-competition-and-consumer-commission-consumer-data-right
- https://www.oaic.gov.au/freedom-of-information/freedom-of-information-guidance-for-government-agencies/proactive-publication-and-administrative-access/information-publication-scheme/information-publication-scheme-survey-2018/summary-report
- https://www.oaic.gov.au/freedom-of-information/freedom-of-information-guidance-for-government-agencies/proactive-publication-and-administrative-access/information-publication-scheme/information-publication-scheme-survey-2018/full-report
A+Domain Intelligenceoaic.gov.au — via Department of Finance, hosted on SQUIZ-AS-AP Squiz Pty Ltd, AUPASS
Unknown
64 days
Issued by Let's Encrypt
Unknown
Not enabled
Protects against DNS spoofing
SQUIZ-AS-AP Squiz Pty Ltd, AU
ASN AS55532
43.245.41.125
Department of Finance
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