Skip to content
https://wa.gov.au

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 3 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.wa.gov.au/
200https://wa.gov.au/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://wa.gov.au/ → https://www.wa.gov.au/

Consistent

B
TLS Certificate Expiry & Recommendations
229 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

229
days left
0d 30d 60d 90d+

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 Records
4 A records, 169 ms lookup
PASS
4 A records, 169 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 99.83.186.106, 75.2.43.150, 76.223.34.124, 13.248.160.137
Info::
No IPv6 (AAAA) records
Info::
5 nameserver(s) configured
Got: t.au, q.au, r.au, s.au, a.au
Info::
1 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 169 ms
Got: 169 ms
A99.83.186.106, 75.2.43.150, 76.223.34.124, 13.248.160.137
AAAA—
CNAME—
NSt.au, q.au, r.au, s.au, a.au
MX
0 wa-gov-au.mail.protection.outlook.com
TXT
MS=ms33428004
office365
SPF v=spf1 include:amazonses.com include:spf.protection.outlook.com -all
24/01/2023
CAALookup not available with standard resolver
Resolved in 169 ms

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A
Redirect Chain
1 redirect(s), 604 ms total
PASS
1 redirect(s), 604 ms total
Info::
Single redirect
Got: https://wa.gov.au → https://www.wa.gov.au/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 604 ms total
Got: 604 ms

https://wa.gov.au

478 ms · HTTP/1.1

301

https://www.wa.gov.au/

126 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://wa.gov.au301478 msHTTP/1.1urllo
2https://www.wa.gov.au/200126 msHTTP/1.1Apache/2.4.62 (Amazon Linux) OpenSSL/3.0.8

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 12 URLs
PASS
robots.txt present, sitemap with 12 URLs
Info::
robots.txt is present
Got: 2173 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 12 entries
Info::
Sitemap index with 12 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 2173 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
#

# robots.txt

#

# This file is to prevent the crawling and indexing of certain parts

# of your site by web crawlers and spiders run by sites like Yahoo!

# and Google. By telling these "robots" where not to go on your site,

# you save bandwidth and server resources.

#

# This file will be ignored unless it is at the root of your host:

# Used:    http://example.com/robots.txt

# Ignored: http://example.com/site/robots.txt

#

# For more information about the robots.txt standard, see:

# http://www.robotstxt.org/robotstxt.html


User-agent: *

# CSS, JS, Images

Allow: /core/*.css$

Allow: /core/*.css?

Allow: /core/*.js$

Allow: /core/*.js?

Allow: /core/*.gif

Allow: /core/*.jpg

Allow: /core/*.jpeg

Allow: /core/*.png

Allow: /core/*.svg

Allow: /profiles/*.css$

Allow: /profiles/*.css?

Allow: /profiles/*.js$

Allow: /profiles/*.js?

Allow: /profiles/*.gif

Allow: /profiles/*.jpg

Allow: /profiles/*.jpeg

Allow: /profiles/*.png

Allow: /profiles/*.svg

# Directories

Disallow: /core/

Disallow: /profiles/

# Files

Disallow: /README.md

Disallow: /composer/Metapackage/README.txt

Disallow: /composer/Plugin/ProjectMessage/README.md

Disallow: /composer/Plugin/Scaffold/README.md

Disallow: /composer/Plugin/VendorHardening/README.txt

Disallow: /composer/Template/README.txt

Disallow: /modules/README.txt

Disallow: /sites/README.txt

Disallow: /themes/README.txt

Disallow: /web.config

# Paths (clean URLs)

Disallow: /admin/

Disallow: /comment/reply/

Disallow: /filter/tips

Disallow: /node/add/

Disallow: /search/

Disallow: /user/register

Disallow: /user/password

Disallow: /user/login

Disallow: /user/logout

Disallow: /media/oembed

Disallow: /*/media/oembed

# Paths (no clean URLs)

Disallow: /index.php/admin/

Disallow: /index.php/comment/reply/

Disallow: /index.php/filter/tips

Disallow: /index.php/node/add/

Disallow: /index.php/search/

Disallow: /index.php/user/password

Disallow: /index.php/user/register

Disallow: /index.php/user/login

Disallow: /index.php/user/logout

Disallow: /index.php/media/oembed

Disallow: /index.php/*/media/oembed

Disallow: /search-results.html

Disallow: /*?keyword=* 

Disallow: /*?q=*
sitemap.xml 200 OK
Type Sitemap Index URLs 12 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
wa.gov.au — via auDA Internal (9999), hosted on AWS
PASS
wa.gov.au — via auDA Internal (9999), hosted on AWS
Info::
DNSSEC is enabled
Info::
Registrar: auDA Internal (9999)
Warning::
Registrar lock is NOT enabled
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.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

Unknown

SSL certificate

229 days

Issued by DigiCert Inc

Domain age

Unknown

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

75.2.43.150

Registrar

auDA Internal (9999)

Unlocked 5 NS records
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar auDA Internal (9999)
Last Updated March 19, 2024
Name Servers t.au, r.au, q.au, s.au, a.au
DNSSEC Enabled
Hosting
IP Address 75.2.43.150
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.5s)

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.

Why this matters

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

A
HTTP Probe Timing
Total 495 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
32 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
153 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
155 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
495 ms
Total Time Total request time from DNS lookup through full response.
495 ms

Connection waterfall

DNS Lookup 32 ms TCP Connect 153 ms TLS Handshake 155 ms Server Processing 155 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback