Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BRedirect Chain1 redirect(s), 1105 ms totalREVIEW
https://surrey.ac.uk
515 ms · HTTP/1.1
https://www.surrey.ac.uk/
590 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://surrey.ac.uk | 301 | 515 ms | HTTP/1.1 | |
| 2 | https://www.surrey.ac.uk/ | 200 | 590 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations160 days until leaf cert expires — 5 issues to addressREVIEW
Certificate validity
Recommended actions
- Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
- Add includeSubDomains to the HSTS directive
- 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
ADNS Records1 A records, 465 ms lookupPASS
| A | 131.227.132.127 |
| AAAA | — |
| CNAME | — |
| NS | ns3.ja.net, apextdns1.surrey.ac.uk, mpextdns1.surrey.ac.uk |
| MX | 0 surrey-ac-uk.mail.protection.outlook.com |
| TXT | 7jl7vdr9zfsljdgl4xkr6525hj6zyv66 apple-domain-verification=i5415X4pWhgi5CDc onetrust-domain-verification=676173a2ee284495bb6978f526a78cb7 msfpkey=38ca66p13k1fogeseu103o3q5 google-site-verification=_mRAT11ooIiZQcm0ws-maxtjOOwj-NQ3f_mEOsQZ9MQ atlassian-domain-verification=mZqNmB95wOk7RxXCYbpGky6nVPoTRrIZ91kSZt00bbzNEuiEnP... atlassian-sending-domain-verification=a35fbaa4-5a24-4df8-b9c3-0a6efc60d9c3 google-site-verification=reRFT1nGogQN_G0B5OKTkQVfC5Q24i9n4L_ni6Q1gZM google-site-verification=e4KG3GziM6G4gSl7mbO29JjivAXu7DXy43D4xvsLp_M d365mktkey=UqPNr7lBIkx8fxYarmNULlD7xAOhEqcEbtQHJ0twPN8x d365mktkey=iytifmxh5HyTabhff7xZtVGAUH1L4nPWks9yHAChYWYx 8WOK696I7ISNU7RBLVP3R6X98VIPE37C0PYRBEQLX onetrust-domain-verification=f8262fd7f7c24a00af35d4e256da6ce7 _3a4bc7ca8676a41579d3735fdc0a464a.pg-prospectus.surrey.ac.uk.CNAME_1a7c610daf35d... SPF v=spf1 include:_u.surrey.ac.uk._spf.smart.ondmarc.com ~all _a0odyxopyo9jga0rbkrdxl37bjz74c2 _globalsign-domain-verification=I_kNQcUM8EY9Bdoua_JHghq-sgxBphmqdVa09jpv5U _globalsign-domain-verification=MWBwAh6ZFdKMhT9zOoD2putKiSaUYsFU8arOo8q4Nn |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
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.
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.
DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.
Source: DNS performance benchmarks
A+Crawlabilityrobots.txt present, sitemap with 7 URLsPASS
#
# 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
Sitemap: https://www.surrey.ac.uk/sitemap.xml
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.txt
Disallow: /web.config
# 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: /news-list/
Disallow: /people-list/
Disallow: /section-list/
Disallow: /taxonomy/
Disallow: /login/
# 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/news-list/
Disallow: /index.php/people-list/
Disallow: /index.php/section-list/
Disallow: /index.php/taxonomy/
User-agent: FunnelBack
# 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.txt
Disallow: /web.config
# 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: /login/
# 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/
- https://www.surrey.ac.uk/sitemap.xml?pag...
- https://www.surrey.ac.uk/sitemap.xml?pag...
- https://www.surrey.ac.uk/sitemap.xml?pag...
- https://www.surrey.ac.uk/sitemap.xml?pag...
- https://www.surrey.ac.uk/sitemap.xml?pag...
- https://www.surrey.ac.uk/sitemap.xml?pag...
- https://www.surrey.ac.uk/sitemap.xml?pag...
A+Domain Intelligencesurrey.ac.uk — via No registrar listed. This domain is directly registered with Nominet., hosted on JANET Jisc Services Limited, GBPASS
Unknown
160 days
Issued by DigiCert Inc
Unknown
Status unknown
Protects against DNS spoofing
JANET Jisc Services Limited, GB
ASN AS786
131.227.132.127
No registrar listed. This domain is directly registered with Nominet.
Expiry timeline
Recommended actions
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
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.
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