Skip to content
https://qut.edu.au

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
80
GRADE
B
FIX
1
REVIEW
5
PASS
3
INFO
0
Probed from Madrid, Spain
302 Found
Checks
9
3 PASS 5 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.

B
Redirect Chain
1 redirect(s), 1567 ms total
REVIEW
1 redirect(s), 1567 ms total
Info::
Single redirect
Got: https://qut.edu.au → https://www.qut.edu.au/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://qut.edu.au
Warning::
Redirect overhead: 1567 ms total
Got: 1567 ms

https://qut.edu.au

1195 ms · HTTP/1.0

302

https://www.qut.edu.au/

371 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://qut.edu.au3021195 msHTTP/1.0BigIP
2https://www.qut.edu.au/403371 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

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

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
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
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.

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

Connection waterfall

DNS Lookup 324 ms TCP Connect 298 ms TLS Handshake 599 ms Server Processing 298 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
146 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

146
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
  • 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, 914 ms lookup
PASS
1 A records, 914 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 131.181.196.203
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns1.qut.edu.au, ns2.qut.edu.au, ns3a.qut.edu.au
Info::
2 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 (914 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 914 ms
A131.181.196.203
AAAA
CNAME
NSns1.qut.edu.au, ns2.qut.edu.au, ns3a.qut.edu.au
MX
2 mxb-00358201.gslb.pphosted.com
2 mxa-00358201.gslb.pphosted.com
TXT
atlassian-domain-verification=Iaj7JT9LPj9oiJ9y6vMOCBLfvfxi3NQmynnbneCXbKm/I+QPHv...
_9osa7l1o2w0ss1120kpi3r6vfi690ak
jamf-site-verification=17ylob_my4Xn6_ThLrFn4w
622917c0-0b2b-48e9-b7f1-085d30cab032
dropbox-domain-verification=09t0ftidn0pk
00d5g000001fdgjeao
nearmap-domain-verification=71732db616512080a92007dd77dfdbcb8be5546e4ed9e875fc75...
MS=ms36987961
adobe-idp-site-verification=e48588b9-0ca9-4b52-9e4a-d23abac88e84
cisco-ci-domain-verification=26030911602c310073b7cecea91387a410d94c91190c33b7453...
docusign=543a3283-bd62-4e61-b88b-a168c48ed941
SPF v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all
google-site-verification=aNa9pcpooqA8Mb17vfbVz2-LFyCYATnoKV8X9dQT55o
b9CQZ5uNcOi2xDTcApTeIHA3M/jlS9we98AY17jF3QPMjcA3xrHakbrr9HwumwG5HK33k7ZU+AQdsd6F...
ms-domain-verification=1e56fd7f-ede3-4b96-8ff5-991c059bfe39
_stwe0v8ontbg2vll6bx1x1orfgoo2i0
apple-domain-verification=ZKidP1yQaXvNbkEN
d24k12xhhpr6vs7bfsnpy6z6ln5smxwq
have-i-been-pwned-verification=5de88401e4a264c506ba320e49a37383
_iedlpu7t4ee7txm0tgf29qywngxbajn
CAALookup not available with standard resolver
Resolved in 914 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
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

403https://www.qut.edu.au/
200https://qut.edu.au/

HTTP → HTTPS

302http://qut.edu.au/ https://www.qut.edu.au/

Use 301 (permanent) instead of 302 (temporary)

A+
Domain Intelligence
qut.edu.au — via Education Services Australia Limited, hosted on AARNET-AS-AP Australian Academic and Research Network AARNet, AU
PASS
qut.edu.au — via Education Services Australia Limited, hosted on AARNET-AS-AP Australian Academic and Research Network AARNet, AU
Info::
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.
Info::
Registrar: Education Services Australia Limited
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: AARNET-AS-AP Australian Academic and Research Network AARNet, AU
Got: AS7575
Domain expiry

Unknown

SSL certificate

146 days

Issued by DigiCert Inc

Domain age

Unknown

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

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

ASN AS7575

131.181.196.203

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 25, 2025
Name Servers ns1.qut.edu.au, ns2.qut.edu.au, ns3a.qut.edu.au
DNSSEC Not enabled
Hosting
IP Address 131.181.196.203
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.6s)

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback