Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.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: *
Disallow: /share/
Disallow: /dev/*
Disallow: /*/_resources/aside*
Disallow: /*/_resources/*/aside*
Disallow: /queensland-travel-declaration-form
Disallow: /queensland-travel-declaration/qld-travel-declaration
Disallow: /queensland-travel-declaration-2/
Disallow: /forgov-dev
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 & Recommendations161 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
A+DNS Records2 A records, 143 ms lookupPASS
| A | 13.248.211.240, 76.223.71.186 |
| AAAA | — |
| CNAME | — |
| NS | a.au, q.au, r.au, s.au, t.au |
| MX | 10 mailer4.mail.qld.gov.au 10 mailer3.mail.qld.gov.au 50 mx01.citec.com.au 50 mx02.citec.com.au |
| TXT | SPF v=spf1 include:spf.wog.mail.qld.gov.au -all _globalsign-domain-verification=cNBAPZWqQgABv3bWXbGvrdGmfZQfvgTXB4XX8K8g_q |
| 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), 346 ms totalPASS
https://qld.gov.au
207 ms · HTTP/1.1
https://www.qld.gov.au:443/
140 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://qld.gov.au | 301 | 207 ms | HTTP/1.1 | awselb/2.0 |
| 2 | https://www.qld.gov.au:443/ | 200 | 140 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
A+Domain Intelligenceqld.gov.au — via auDA Internal (9999), hosted on AWSPASS
Unknown
161 days
Issued by Amazon
Unknown
Enabled
Protects against DNS spoofing
AWS
ASN AS16509
13.248.211.240
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