Infrastructure - https://nla.gov.au BeaverCheck Audit

D

Redirect Chain

Action

2 redirect(s), 3256 ms total

FIX

2 redirect(s), 3256 ms total

2 redirects before reaching final URL

Each redirect adds latency. Try to minimize the chain to 1 hop.

WWW normalization redirect

Uses 302 (temporary) redirect

If permanent, use 301 instead.

Got: https://nla.gov.au

Redirect overhead: 3256 ms total

Got: 3256 ms

Cross-domain redirect detected

https://nla.gov.au

838 ms · HTTP/1.1

302

https://www.nla.gov.au/

1762 ms · HTTP/1.1

301

https://www.library.gov.au

656 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://nla.gov.au	302	838 ms	HTTP/1.1	nginx
2	https://www.nla.gov.au/	301	1762 ms	HTTP/1.1	nginx
3	https://www.library.gov.au	200	656 ms	HTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

If permanent, use 301 instead.

Why this matters

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

D

CDN & Delivery

Action

No CDN detected

FIX

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

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

Crawlability

no robots.txt, no sitemap

REVIEW

no robots.txt, no sitemap

No robots.txt found

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

No sitemap.xml found

A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more ▾

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

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

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B

HTTP Probe Timing

Total 1141 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

REVIEW

DNS Lookup

305 ms

TCP Connect

277 ms

TLS Handshake

283 ms

Time to First Byte

1.14 s

Total Time

1.14 s

Connection waterfall

DNS Lookup 305 ms TCP Connect 277 ms TLS Handshake 283 ms Server Processing 277 ms Content Transfer 0 ms

B

TLS Certificate Expiry & Recommendations

69 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

69

days left

0d 30d 60d 90d+

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

A

DNS Records

1 A records, 2047 ms lookup

PASS

1 A records, 2047 ms lookup

Resolves to 1 IPv4 address(es)

Got: 192.102.239.32

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

5 nameserver(s) configured

Got: smtpgate.nla.gov.au, ns1.aarnet.net.au, ns3.aarnet.net.au, ns1.nla.gov.au, ns2.aarnet.net.au

1 mail exchanger(s) configured

CAA records not checked

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

SPF record present in TXT

DNS resolution is slow (2047 ms)

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Got: 2047 ms

A	192.102.239.32
AAAA	—
CNAME	—
NS	smtpgate.nla.gov.au, ns1.aarnet.net.au, ns3.aarnet.net.au, ns1.nla.gov.au, ns2.aarnet.net.au
MX	0 nla-gov-au.mail.protection.outlook.com
TXT	SPF v=spf1 include:_spf.createsend.com include:spf.protection.outlook.com include:m... _dddabkl5t0sylvufjl498w3lls5t9qf google-site-verification=22n3NusTgBF1Z676SbNeHUhehIUSEsgPRRZfdZsG3_I atlassian-domain-verification=H7TggyJ5c7WygP7T36AZi6VoUrbhT4sHPaj4gnQ0OvBEsDSbDR... apple-domain-verification=0lpnzLDj1gf7Xsxi slack-domain-verification=UnGR4V6jllO74pBcadwm2oo7haHFVPlsot3lpSef Location=P google-site-verification=RDVBED6zn0epVQkslGKmy0190K-hW3_AEvCsTLBcSFc ahrefs-site-verification_2aaa26619ccdb102f839b4edfc5657278ab2609a181f083c3277c3e... MS=ms57340175 atlassian-domain-verification=nmViGVY/tEQ5C6C4/9MRI2zTwUiJbjmXyEjTGXz4GvnupdWiHO... google-site-verification=vUrNbcoYJqaSjqeAKxMH75zDD6NVm1Z0FQizHhrZrMk google-site-verification=vnKBHeOytgo3Kv4BzfGixms733jYyky2rc8C2a4FhXo cZ83yErsg4INnAmVaeD4EwYSrQ+cZLyxiGEEU1Y76wUBk0x+p71Adv24LXYHKfeEETXnWTcskq+ITNUg... sophos-domain-verification=d2a36d77c1d75afb3f42a7013fc858588438a5b950682c09b7973... ZOOM_verify_oScA1GtLTYiqqRtsvnJRpw
CAA	Lookup not available with standard resolver

Resolved in 2047 ms

Multiple A records provide failover if one server goes down.

Why this matters

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.

Why this matters

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.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

PASS

www/non-www, trailing slash, HTTP→HTTPS

www/non-www redirect configured correctly (preferred: non-www)

HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.nla.gov.au/

200https://nla.gov.au/

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A+

Domain Intelligence

nla.gov.au — via Department of Finance, hosted on NATIONAL-LIBRARY-AU National Library of Australia, AU

PASS

nla.gov.au — via Department of Finance, hosted on NATIONAL-LIBRARY-AU National Library of Australia, AU

DNSSEC is not enabled

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Registrar: Department of Finance

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.

Hosting: NATIONAL-LIBRARY-AU National Library of Australia, AU

Got: AS4822

Domain expiry

Unknown

SSL certificate

69 days

Issued by Let's Encrypt

Domain age

Unknown

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

NATIONAL-LIBRARY-AU National Library of Australia, AU

ASN AS4822

192.102.239.32

Registrar

Department of Finance

Unlocked 5 NS records

Expiry timeline

Today

+1 year

SSL expiry Danger zone (≤30 days)

Recommended actions

Enable DNSSEC to protect visitors from DNS spoofing
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar Department of Finance

Last Updated April 6, 2026

Name Servers ns1.nla.gov.au, smtpgate.nla.gov.au, ns2.aarnet.net.au, ns1.aarnet.net.au, ns3.aarnet.net.au

DNSSEC Not enabled

Hosting

IP Address 192.102.239.32

ASN AS4822 (NATIONAL-LIBRARY-AU National Library of Australia, AU)

Provider NATIONAL-LIBRARY-AU National Library of Australia, AU

Data source: rdap (0.7s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

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.

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