Infrastructure - https://anu.edu.au BeaverCheck Audit

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.

B

Redirect Chain

1 redirect(s), 2967 ms total

REVIEW

1 redirect(s), 2967 ms total

Single redirect

Got: https://anu.edu.au → https://www.anu.edu.au/ (301)

WWW normalization redirect

Redirect overhead: 2967 ms total

Got: 2967 ms

https://anu.edu.au

1346 ms · HTTP/1.1

301

https://www.anu.edu.au/

1621 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://anu.edu.au	301	1346 ms	HTTP/1.1	nginx
2	https://www.anu.edu.au/	200	1621 ms	HTTP/1.1	nginx

See the visual redirect chain in the HTTP Probe tab →

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

C

URL Variants

Action

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

REVIEW

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

Both www and non-www versions serve content

Got: Both variants return 200 Expected: One variant 301-redirects to the other

HTTP→HTTPS redirect uses 302 instead of 301

Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.anu.edu.au/

200https://anu.edu.au/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://anu.edu.au/ → https://anu.edu.au/

Use 301 (permanent) instead of 302 (temporary)

B

HTTP Probe Timing

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

REVIEW

DNS Lookup

278 ms

TCP Connect

201 ms

TLS Handshake

413 ms

Time to First Byte

1.09 s

Total Time

1.09 s

Connection waterfall

DNS Lookup 278 ms TCP Connect 201 ms TLS Handshake 413 ms Server Processing 202 ms Content Transfer 0 ms

B

TLS Certificate Expiry & Recommendations

85 days until leaf cert expires — 4 issues to address

REVIEW

Certificate validity

85

days left

0d 30d 60d 90d+

Recommended actions

Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
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, 279 ms lookup

PASS

1 A records, 279 ms lookup

Resolves to 1 IPv4 address(es)

Got: 130.56.67.33

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

3 nameserver(s) configured

Got: ns1.anu.edu.au, ns.adelaide.edu.au, una.anu.edu.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 (279 ms)

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

Got: 279 ms

A	130.56.67.33
AAAA	—
CNAME	—
NS	ns1.anu.edu.au, ns.adelaide.edu.au, una.anu.edu.au
MX	10 anu-edu-au.mail.protection.outlook.com
TXT	miro-verification=1d0b102670be0bd291a303f4ff2b5443b208b138 google-site-verification=XXn4tsSQVkQ7iiGVIGSQAOdXil_PUTJZ0-t3Ax4ljc4 QuoVadis=0cd92696-63ea-44b1-8bd9-39ba6bc92d19 google-gws-recovery-domain-verification=50311553 QA47EYZ56VMI4MCUS6U412C402S9SVJ9A15FSN48N docusign=5a9d5e75-1f73-4ebd-8d60-e7c7e258a404 79DD995D-6451-444E-9077-0A30703A3D42 docusign=ec22b91d-c927-4af6-b2d5-afbae05f3c3f 66576d17-3d04-455c-afdf-af5d52bcdf56 google-site-verification=a73Q9ODC5ullPbr8T2p85d4LW4XhfQ5WZJn1UlfcqCA apple-domain-verification=dn5ZYjIejeP9693a atlassian-domain-verification=QonxBf9MDsLZSGKednnjfVaKjH2CzRNOesVbAvFbTMgmnmUPhi... SPF v=spf1 include:4501nxl41s.powerspf.com include:spf.protection.outlook.com -all adobe-idp-site-verification=c7deea66579c60460784c5b507595d6f3599f5cc482d65445a4f... atlassian-domain-verification=QQWDXeeq1llnkaWxhkUH3Wk9cvOdmmrudLsNMZNGocrmoZIubi... samsung-domain-verification=63700cfc-13ae-4f02-9b74-5cdddc0918de
CAA	Lookup not available with standard resolver

Resolved in 279 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+

Crawlability

robots.txt present, sitemap with 72 URLs

PASS

robots.txt present, sitemap with 72 URLs

robots.txt is present

Got: 2005 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 72 entries

Sitemap index with 72 child sitemaps

robots.txt does not reference a 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 2005 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
# 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

sitemap.xml 200 OK

Type Sitemap Index URLs 72 entries Valid XML Yes

Child Sitemaps:

A+

Domain Intelligence

anu.edu.au — via Education Services Australia Limited, hosted on AARNET-AS-AP Australian Academic and Research Network AARNet, AU

PASS

anu.edu.au — via Education Services Australia Limited, hosted on AARNET-AS-AP Australian Academic and Research Network AARNet, 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: Education Services Australia Limited

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: AARNET-AS-AP Australian Academic and Research Network AARNet, AU

Got: AS7575

Domain expiry

Unknown

SSL certificate

85 days

Issued by Sectigo Limited

Domain age

Unknown

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AARNET-AS-AP Australian Academic and Research Network AARNet, AU

ASN AS7575

130.56.67.33

Registrar

Education Services Australia Limited

Unlocked 3 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 Education Services Australia Limited

Last Updated August 4, 2025

Name Servers una.anu.edu.au, ns.adelaide.edu.au, ns1.anu.edu.au

DNSSEC Not enabled

Hosting

IP Address 130.56.67.33

ASN AS7575 (AARNET-AS-AP Australian Academic and Research Network AARNet, AU)

Provider AARNET-AS-AP Australian Academic and Research Network AARNet, AU

Data source: rdap (0.8s)

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