Skip to content
https://manchester.ac.uk

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
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
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.

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.manchester.ac.uk/
200https://manchester.ac.uk/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://manchester.ac.uk/ https://www.manchester.ac.uk/

Consistent

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

Certificate validity

161
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, 35 ms lookup
PASS
1 A records, 35 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 18.133.51.167
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: ns4.ja.net, ns2.manchester.ac.uk, ns1.manchester.ac.uk
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
Info::
DNS resolution time: 35 ms
Got: 35 ms
A18.133.51.167
AAAA
CNAME
NSns4.ja.net, ns2.manchester.ac.uk, ns1.manchester.ac.uk
MX
10 mxa-0053d701.gslb.pphosted.com
10 mxb-0053d701.gslb.pphosted.com
TXT
globalsign-domain-verification=C4BF0E79BF41F98B9B6FCA2F19185016
have-i-been-pwned-verification=dweb_kne1y9modsxhzj7iyn4x33yr
SPF v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com include:servers.ebsnd.com ~a...
klaviyo-site-verification=WBwv7U
IrtxI7j8sGpIVRkg15wwbxd1zm4HSSRvPiJW24tWkcLe/fGgf8RUCIAFQGZ9v0j3jA7raPRUhNrLgotC...
bw=OON2mN4yVYjYhqJ269Kjx1utEoxFXrZIQJW9OAFnvQ7k
duo_sso_verification=c5z5IvYVnNPfYvRklpnKKSNk1nAapRFNlHD0lXjsxOptecJeaGFQ7YhweUi...
atlassian-domain-verification=DTclkewWdE4wjvI/3OSjwuSCRTV41v/RPZyYKRnHGkSpgMIoIv...
hcp-domain-verification=d195396d1af0e50f07cd2822981682aaa8bdcb456cf5af2ebc091d26...
klaviyo-site-verification=UXLTcK
google-site-verification=bCMX5_dpJPxRLyMi9sSLkfHTC8Eytw0V9ABPnFNWP5E
google-gws-recovery-domain-verification=55206467
hibp-verify=dweb_3ukwusushj4ir5oeayz3tl7r
CAALookup not available with standard resolver
Resolved in 35 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
Redirect Chain
1 redirect(s), 271 ms total
PASS
1 redirect(s), 271 ms total
Info::
Single redirect
Got: https://manchester.ac.uk → https://www.manchester.ac.uk/ (301)
Info::
WWW normalization redirect

https://manchester.ac.uk

105 ms · HTTP/1.1

301

https://www.manchester.ac.uk/

166 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://manchester.ac.uk301105 msHTTP/1.1Apache/2.4.62 () OpenSSL/1.0.2k-fips PHP/5.4.16
2https://www.manchester.ac.uk/200166 msHTTP/1.1Apache

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 8 URLs
PASS
robots.txt present, sitemap with 8 URLs
Info::
robots.txt is present
Got: 434 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 8 entries
Info::
Sitemap index with 8 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 434 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /_contentlibrary/

Disallow: /medialibrary/

Allow: /medialibrary/assets/

Disallow: /search/

Disallow: /AllianceReport2020

Disallow: /studentsupportreport2020

Disallow: /study/humanities-campaigns/

Disallow: /study/masters/humanities-campaigns/

Disallow: /study/undergraduate/fse-campaigns/

Disallow: /study/undergraduate/humanities-campaigns/


Sitemap: https://www.manchester.ac.uk/sitemap-index.xml
A+
Domain Intelligence
manchester.ac.uk — via No registrar listed. This domain is directly registered with Nominet., hosted on AWS
PASS
manchester.ac.uk — via No registrar listed. This domain is directly registered with Nominet., hosted on AWS
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: AWS
Got: AS16509
Domain expiry

Unknown

SSL certificate

161 days

Issued by Sectigo Limited

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

18.133.51.167

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 18.133.51.167
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: whois (0.8s)

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

Connection waterfall

DNS Lookup 29 ms TCP Connect 25 ms TLS Handshake 54 ms Server Processing 25 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