Skip to content
https://auckland.ac.nz

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
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
Redirect Chain
Action
2 redirect(s), 2632 ms total
FIX
2 redirect(s), 2632 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Warning::
Redirect overhead: 2632 ms total
Got: 2632 ms

https://auckland.ac.nz

5 ms · HTTP/1.1

301

https://www.auckland.ac.nz/

1296 ms · HTTP/1.1

301

https://www.auckland.ac.nz/en.html

1331 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://auckland.ac.nz3015 msHTTP/1.1
2https://www.auckland.ac.nz/3011296 msHTTP/1.1
3https://www.auckland.ac.nz/en.html2001331 msHTTP/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

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

C
HTTP Probe Timing
Action
Total 1586 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
341 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
0 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
3 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.59 s
Total Time Total request time from DNS lookup through full response.
1.59 s

Connection waterfall

DNS Lookup 341 ms TCP Connect 0 ms TLS Handshake 3 ms Server Processing 1.24 s Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
153 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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
4 A records, 1884 ms lookup
PASS
4 A records, 1884 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 151.101.3.10, 151.101.195.10, 151.101.67.10, 151.101.131.10
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: dns1.auckland.ac.nz, dns2.auckland.ac.nz
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
Warning::
DNS resolution is slow (1884 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 1884 ms
A151.101.3.10, 151.101.195.10, 151.101.67.10, 151.101.131.10
AAAA—
CNAME—
NSdns1.auckland.ac.nz, dns2.auckland.ac.nz
MX
0 auckland-ac-nz.mail.protection.outlook.com
TXT
QuoVadis=488bbb06-15cb-4dd5-920d-2addb0ce8dfe
atlassian-domain-verification=XcdLKb1LJUg0ov7JyR/83WCTYBJvixKtYYQCY5dZkm7bd00qOw...
QuoVadis=b9e39938-386b-4593-98f8-5f4606a9e3c3
SPF v=spf1 include:spf.protection.outlook.com include:service-now.com include:rnmk.c...
_0gpc6kwcy64y8elsc2k4tpfhogiors9
52cysrqtfdtvc8bf9z4b00nsl4vw2qkl
google-site-verification=txk6bKhXkblTHjKCWO_UNEwqb_IRtzEzF5sbP34SpcY
fadudspqbcafrlqoqig3ls99v0
jamf-site-verification=AQFEbmp4uYM2QuG7ZIcnCQ
fC0a0/QulrMsyaznlj/M9LQZFO/sXMEkBSb1UMaH+aXgAwm5iK7ZuzhnNs0jkf/1atNlawPe+6hWweCW...
facebook-domain-verification=l72t2w1cy7nvenpgd5jvswdzk3nwve
google-site-verification=R7lbbM9UdBuh5ts2SK2CzxlI0wRL3C_j1qrq4MCtP4s
google-site-verification=eIcbnPutWjqMLoT5KNuya1KF_WeJlTmbO0_5sXyqnD0
gmyl112szjqj3r2sdch2dlxc4ck1bsq6
google-site-verification=bkMLIKq9yCntHLqYuiv1JoqMa-ZbKXQE9TZ9NE0
adobe-idp-site-verification=494edb15-28b9-48df-baa9-a26e0a8a316c
cloudhealth=9f334fc4-a5b1-498a-b99a-c5126c6510b8
apple-domain-verification=vn90QYKAwTYJujqf
dropbox-domain-verification=yg3oqpedtryw
CAALookup not available with standard resolver
Resolved in 1884 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.

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 1 URLs
PASS
robots.txt present, sitemap with 1 URLs
Info::
robots.txt is present
Got: 76 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1 entries
Info::
Sitemap index with 1 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 76 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /
Sitemap: https://www.auckland.ac.nz/sitemap-index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 1 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.auckland.ac.nz/
200https://auckland.ac.nz/

Preferred variant: non-www

HTTP → HTTPS

301http://auckland.ac.nz/ → https://auckland.ac.nz/

Consistent

A+
Domain Intelligence
auckland.ac.nz — via Netregistry PTY Ltd/TA Webcentral and Melbourne IT, 29 years, 9 months old, hosted on Fastly
PASS
auckland.ac.nz — via Netregistry PTY Ltd/TA Webcentral and Melbourne IT, 29 years, 9 months old, hosted on Fastly
Info::
Registrar: Netregistry PTY Ltd/TA Webcentral and Melbourne IT
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: Fastly
Got: AS54113
Domain expiry

Unknown

SSL certificate

153 days

Issued by DigiCert Inc

Domain age

29 years, 9 months

Registered December 8, 1996

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Fastly

ASN AS54113

151.101.67.10

Registrar

Netregistry PTY Ltd/TA Webcentral and Melbourne IT

Unlocked 2 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 Netregistry PTY Ltd/TA Webcentral and Melbourne IT
Created December 8, 1996 (29 years, 9 months ago)
Last Updated January 8, 2026
Name Servers dns1.auckland.ac.nz, dns2.auckland.ac.nz
Hosting
IP Address 151.101.67.10
ASN AS54113 (FASTLY - Fastly, Inc., US)
Provider Fastly
Data source: whois (1.2s)

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
CDN & Delivery
Fastly (MISS)
PASS
Fastly (MISS)
Info::
Site is served via Fastly CDN
Got: x-served-by: cache-toj-leto2350031-TOJ, cache-toj-leto2350031-TOJ
Info::
CDN cache status: MISS
CDN Detected: Fastly
Provider Fastly Cache Status MISS Evidence x-served-by: cache-toj-leto2350031-TOJ, cache-toj-leto2350031-TOJ
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback