Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.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: *
Crawl-delay: 10
Disallow: /*?sq_content_src=
Disallow: /*_recache
Disallow: /*_performance
Disallow: /*_web_services
Disallow: /global-contacts
Disallow: /editors
User-agent: Funnelback
Disallow: /*_design
No sitemap found
Adding a sitemap helps search engines discover your pages.
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations180 days until leaf cert expires — 2 issues to addressREVIEW
Certificate validity
Recommended actions
- Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
BCDN & DeliveryCloudflareREVIEW
A+DNS Records2 A records, 4 ms lookupPASS
| A | 162.159.142.74, 172.66.2.70 |
| AAAA | 2a06:98c1:58::23e, 2606:4700:7::23e |
| CNAME | — |
| NS | a.au, q.au, r.au, s.au, t.au |
| MX | 10 sa-gov-au.mail.protection.outlook.com |
| TXT | 15012021 ms=ms36033267 t3bglg7qk03v67wnjgfry40r5hhhkngt google-site-verification=YMbIjZl7DB7Ey16fkMt_YJPInj3OKdAPXvJrcj95geI SPF v=spf1 mx a:spf.protection.sa.gov.au include:spf.protection.outlook.com -all /lxeyayzmwnu9lkr4eqn1gzywyxfwchs8ug9phxul0nxr/dauue3hf5wdriupwzt5ova1py1bobnm8nh... 1sabQ3fA/hNMfZRNCk4M6TCQxildKkQizrTtaL+3pPlSK0NEDXZKLsjzwH2lYV+q7pqeWjReYEnast1M... l83ejtdoucisjlj0m4etdy4/n4svhpzuk7fgdxhx1kywngjmdwynr02q37mrywwjf384jwk4tgvvcp5o... adobe-idp-site-verification=19215a379c8f846fa169ad7135b5c794e3981470bfb30ae802e1... cisco-ci-domain-verification=1abedc20bde220dc5dedfe5b433a9d6000b6c46db6838993d88... |
| 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.
ARedirect Chain1 redirect(s), 122 ms totalPASS
https://sa.gov.au
14 ms · HTTP/1.1
https://www.sa.gov.au/
108 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://sa.gov.au | 301 | 14 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.sa.gov.au/ | 200 | 108 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (1 ms)PASS
A+Domain Intelligencesa.gov.au — via auDA Internal (9999)PASS
Unknown
180 days
Issued by CLOUDFLARE, INC.
Unknown
Enabled
Protects against DNS spoofing
Unknown
2a06:98c1:58::23e
auDA Internal (9999)
Expiry timeline
Recommended actions
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
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