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

Infrastructure

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

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

Certificate validity

68
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
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: MAD)
Got: cf-ray: 9f0865845b39342a-MAD
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9f0865845b39342a-MAD
A
DNS Records
1 A records, 2109 ms lookup
PASS
1 A records, 2109 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 43.245.41.70
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: dns3.griffith.edu.au, dns2.griffith.edu.au, dns1.griffith.edu.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
Warning::
DNS resolution is slow (2109 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 2109 ms
A43.245.41.70
AAAA
CNAME
NSdns3.griffith.edu.au, dns2.griffith.edu.au, dns1.griffith.edu.au
MX
0 griffith-edu-au.mail.protection.outlook.com
TXT
facebook-domain-verification=viphrvpgpzvfw7ii9kp7blpnt85x1s
nearmap-domain-verification=0a19e4ecf11bc1c2513387ed72532a8d81ca7c2ea25a8d3b953
nintex.62466ab4f295c6006afb4596
MS=079D6A7D1B18DECE5F0EF251747D1F6CC405FEB0
v=DMARC1;p=reject;rua=mailto:97e85530c1e8887@rep.dmarcanalyzer.com;ruf=mailto:97...
b52cb09a-f5bd-4b6d-ada8-a100e9187c87
atlassian-domain-verification=/kzoja5Iq02FhMC0KF4xApsNTHRMNuv9nfBwGj4iFZGxUKwBod...
smartsheet-site-validation=RExoNVBW4BqwqCzcU02v-u7d6CzGsJqV
google-site-verification=VPKCzSS9Pd1v9jKCITgo-tXE2ceOdN8hCXiU5CUs-CY
MS=B2AEDC0FB0A4B01344E236B4A4E72594DA5EACA6
_yo8ep7uj2cxg29ns06lkxl9nfnlxe4f
cisco-ci-domain-verification=12d31dc30ac8cc66f355bb10bccf39dbb8293a3c1a27a884e74...
google-site-verification=NMeEubMJdVV6NtV4voRfJ1vHefZZQPVjV_MA5oNCaWk
1KGQ8BDVM9541DJIJSJL3GMO65NHZW9IJDYXOIZPB
asv=1c4fd85b8106313ffb9b296b443b98bb
lcdz0bg2wd5170wzv318dp1wszdp85hx
miro-verification=159c8fe242cebdc70390504a88870194705416f7
apple-domain-verification=J8TWguBLK9R3R7st
nearmap-domain-verification=0a19e4ecf11bc1c2513387ed72532a8d81ca7c2ea25a8d3b9536...
_xo9vy481a0v3ksqzuv3ihskija1iv4p
adobe-idp-site-verification=d28deb2a-c7d8-421f-97ec-0d2ec9a7a39f
SPF v=spf1 ip4:132.234.227.10/29 ip4:132.234.235.0/24 ip4:132.234.242.0/24 ip4:203.2...
CAALookup not available with standard resolver
Resolved in 2109 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
Redirect Chain
1 redirect(s), 478 ms total
PASS
1 redirect(s), 478 ms total
Info::
Single redirect
Got: https://griffith.edu.au → https://www.griffith.edu.au/ (301)
Info::
WWW normalization redirect

https://griffith.edu.au

33 ms · HTTP/1.1

301

https://www.griffith.edu.au/

445 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://griffith.edu.au30133 msHTTP/1.1cloudflare
2https://www.griffith.edu.au/403445 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

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

HTTP → HTTPS

301http://griffith.edu.au/ https://www.griffith.edu.au/

Consistent

A+
Domain Intelligence
griffith.edu.au — via Education Services Australia Limited, hosted on SQUIZ-AS-AP Squiz Pty Ltd, AU
PASS
griffith.edu.au — via Education Services Australia Limited, hosted on SQUIZ-AS-AP Squiz Pty Ltd, 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: SQUIZ-AS-AP Squiz Pty Ltd, AU
Got: AS55532
Domain expiry

Unknown

SSL certificate

68 days

Issued by DigiCert Inc

Domain age

Unknown

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

SQUIZ-AS-AP Squiz Pty Ltd, AU

ASN AS55532

43.245.41.70

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 June 23, 2024
Name Servers dns3.griffith.edu.au, dns2.griffith.edu.au, dns1.griffith.edu.au
DNSSEC Not enabled
Hosting
IP Address 43.245.41.70
ASN AS55532 (SQUIZ-AS-AP Squiz Pty Ltd, AU)
Provider SQUIZ-AS-AP Squiz Pty Ltd, AU
Data source: rdap (1.1s)

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

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

Connection waterfall

DNS Lookup 333 ms TCP Connect 1 ms TLS Handshake 10 ms Server Processing 17 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