Skip to content
https://st-andrews.ac.uk

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Santa Clara, United States
302 Found
Checks
9
4 PASS 4 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), 1189 ms total
REVIEW
1 redirect(s), 1189 ms total
Info::
Single redirect
Got: https://st-andrews.ac.uk → https://www.st-andrews.ac.uk/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://st-andrews.ac.uk
Warning::
Redirect overhead: 1189 ms total
Got: 1189 ms

https://st-andrews.ac.uk

594 ms · HTTP/1.1

302

https://www.st-andrews.ac.uk/

595 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://st-andrews.ac.uk302594 msHTTP/1.1
2https://www.st-andrews.ac.uk/200595 msHTTP/1.1Apache/2.4.66 (Debian)

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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.st-andrews.ac.uk/
200https://st-andrews.ac.uk/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://st-andrews.ac.uk/ https://www.st-andrews.ac.uk/

Consistent

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

Certificate validity

60
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, 154 ms lookup
PASS
1 A records, 154 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 138.251.7.84
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
5 nameserver(s) configured
Got: ns1.st-and.ac.uk, ns3.st-and.ac.uk, ns4.ja.net, ns4.st-and.ac.uk, ns2.st-and.ac.uk
Info::
5 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
Info::
DNS resolution time: 154 ms
Got: 154 ms
A138.251.7.84
AAAA
CNAME
NSns1.st-and.ac.uk, ns3.st-and.ac.uk, ns4.ja.net, ns4.st-and.ac.uk, ns2.st-and.ac.uk
MX
5 mx04.st-andrews.ac.uk
5 mx05.st-andrews.ac.uk
5 mx02.st-andrews.ac.uk
5 mx03.st-andrews.ac.uk
5 mx01.st-andrews.ac.uk
TXT
adobe-idp-site-verification=c859c3b70420f0fa3c2c0891a4101110fc16c2ee7bb9a0773da6...
gBM5O36SmWsxHRRlgoa29ElwLv+Dr9wkRCThCcPHA9CrwMVsmlW/Db35xAMSdoNQB+Obfy1L3ylOZYMS...
google-site-verification=d3JjGXl44LCRvuWJ1iBzbLHurZEZNso0Kl5Wc0i0zTM
atlassian-domain-verification=c7XXDXRJvxvtdwyDO4BIskEDg5RS6tK2v3ZU2K09EqJr02HJtk...
SPF v=spf1 ip4:138.251.6.248 ip4:138.251.6.249 ip4:138.251.6.241 ip4:138.251.6.250 i...
CAALookup not available with standard resolver
Resolved in 154 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.

A+
Crawlability
robots.txt present, sitemap with 10350 URLs
PASS
robots.txt present, sitemap with 10350 URLs
Info::
robots.txt is present
Got: 602 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 10350 entries
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your 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 602 B Sitemaps referenced 0 User-agents *, PetalBot, SemrushBot, HTTrack Blocking No — crawling allowed
User-agent: *
Crawl-delay: 10
Disallow: /jira/
Disallow: /~www_pa/
Disallow: /~psst/
Disallow: /subjects/archive/
Disallow: /schoolpeoplepublic/*
Disallow: /*?*skin=0
Disallow: /subjects/modules/search/
Disallow: /subjects/modules/advisers-search/
Disallow: /subjects/reqs/
Disallow: /subjects/specs/
Disallow: /philevents/
Disallow: /php/
Disallow: /s/
Disallow: /s1/
Disallow: /search/
Disallow: /collections/
Disallow: /photo-gallery/
Disallow: /guides/index.php
Disallow: /guides/index.html
Disallow: /~awm2/
User-agent: PetalBot
Disallow: /
User-agent: SemrushBot
Disallow: /
User-agent: HTTrack


A+
Domain Intelligence
st-andrews.ac.uk — via No registrar listed. This domain is directly registered with Nominet., hosted on JANET Jisc Services Limited, GB
PASS
st-andrews.ac.uk — via No registrar listed. This domain is directly registered with Nominet., hosted on JANET Jisc Services Limited, GB
Info::
Registrar: No registrar listed. This domain is directly registered with Nominet.
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: JANET Jisc Services Limited, GB
Got: AS786
Domain expiry

Unknown

SSL certificate

60 days

Issued by Let's Encrypt

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

JANET Jisc Services Limited, GB

ASN AS786

138.251.7.84

Registrar

No registrar listed. This domain is directly registered with Nominet.

Unlocked 7 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 No registrar listed. This domain is directly registered with Nominet.
Name Servers ns0.ja.net, ns2.ja.net, ns3.ja.net, ns4.ja.net, auth03.ns.uu.net, ns1.surfnet.nl, dns-3.dfn.de
Registrant The JNT Association
Hosting
IP Address 138.251.7.84
ASN AS786 (JANET Jisc Services Limited, GB)
Provider JANET Jisc Services Limited, GB
Data source: whois (1.3s)

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 591 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
152 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
145 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
148 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
591 ms
Total Time Total request time from DNS lookup through full response.
591 ms

Connection waterfall

DNS Lookup 152 ms TCP Connect 145 ms TLS Handshake 148 ms Server Processing 146 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