Skip to content
https://www.cam.ac.uk

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
95
GRADE
A
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from New York, United Stated
200 OK
Checks
9
7 PASS 2 REVIEW
B
DNS Records
1 A records, 330 ms lookup
REVIEW
1 A records, 330 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 23.185.0.3
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2620:12a:8001::3, 2620:12a:8000::3
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Warning::
DNS resolution is slow (330 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 330 ms
A23.185.0.3
AAAA2620:12a:8001::3, 2620:12a:8000::3
CNAME—
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 330 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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

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

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

Certificate validity

41
days left
0d 30d 60d 90d+

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • 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
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.cam.ac.uk

https://www.cam.ac.uk

171 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.cam.ac.uk200171 msHTTP/1.1nginx
A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2620:12a:8001::3, 2620:12a:8000::3
Got: 1 ms connect
IPv6 Ready
AAAA Records 2620:12a:8001::3, 2620:12a:8000::3 Connection Reachable (1 ms)
A+
Crawlability
robots.txt present, sitemap with 2 URLs
PASS
robots.txt present, sitemap with 2 URLs
Info::
robots.txt is present
Got: 2189 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 2 entries
Info::
Sitemap index with 2 child sitemaps
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 2189 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
#
# 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

User-agent: *
Crawl-delay: 10
# CSS, JS, Images
Allow: /misc/*.css$
Allow: /misc/*.css?
Allow: /misc/*.js$
Allow: /misc/*.js?
Allow: /misc/*.gif
Allow: /misc/*.jpg
Allow: /misc/*.jpeg
Allow: /misc/*.png
Allow: /modules/*.css$
Allow: /modules/*.css?
Allow: /modules/*.js$
Allow: /modules/*.js?
Allow: /modules/*.gif
Allow: /modules/*.jpg
Allow: /modules/*.jpeg
Allow: /modules/*.png
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: /themes/*.css$
Allow: /themes/*.css?
Allow: /themes/*.js$
Allow: /themes/*.js?
Allow: /themes/*.gif
Allow: /themes/*.jpg
Allow: /themes/*.jpeg
Allow: /themes/*.png
# Directories
Disallow: /includes/
Disallow: /misc/
Disallow: /modules/
Disallow: /profiles/
Disallow: /scripts/
Disallow: /themes/
# Files
Disallow: /CHANGELOG.txt
Disallow: /cron.php
Disallow: /INSTALL.mysql.txt
Disallow: /INSTALL.pgsql.txt
Disallow: /INSTALL.sqlite.txt
Disallow: /install.php
Disallow: /INSTALL.txt
Disallow: /LICENSE.txt
Disallow: /MAINTAINERS.txt
Disallow: /update.php
Disallow: /UPGRADE.txt
Disallow: /xmlrpc.php
# 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/
# Paths (no clean URLs)
Disallow: /?q=admin/
Disallow: /?q=comment/reply/
Disallow: /?q=filter/tips/
Disallow: /?q=node/add/
Disallow: /?q=search/
Disallow: /?q=user/password/
Disallow: /?q=user/register/
Disallow: /?q=user/login/
Disallow: /?q=user/logout/
sitemap.xml 200 OK
Type Sitemap Index URLs 2 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.cam.ac.uk/
301https://cam.ac.uk/

Preferred variant: www

HTTP → HTTPS

301http://www.cam.ac.uk/ → https://www.cam.ac.uk/

Consistent

A+
Domain Intelligence
cam.ac.uk — via No registrar listed. This domain is directly registered with Nominet.
PASS
cam.ac.uk — via No registrar listed. This domain is directly registered with Nominet.
Info::
Registrar: No registrar listed. This domain is directly registered with Nominet.
Domain expiry

Unknown

SSL certificate

41 days

Issued by Let's Encrypt

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2620:12a:8001::3

Registrar

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

Lock status unknown 7 NS records
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
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 2620:12a:8001::3
Data source: whois (1.1s)
A+
HTTP Probe Timing
Total 181 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
159 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.
4 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
181 ms
Total Time Total request time from DNS lookup through full response.
182 ms

Connection waterfall

DNS Lookup 159 ms TCP Connect 1 ms TLS Handshake 4 ms Server Processing 17 ms Content Transfer 1 ms
A+
CDN & Delivery
Fastly (HIT, HIT, MISS, MISS)
PASS
Fastly (HIT, HIT, MISS, MISS)
Info::
Site is served via Fastly CDN
Got: x-served-by: cache-ams2100141-AMS, cache-lga21944-LGA, cache-lga21959-LGA, cache-lga21959-LGA
Info::
CDN cache status: HIT, HIT, MISS, MISS
CDN Detected: Fastly
Provider Fastly Cache Status HIT, HIT, MISS, MISS Evidence x-served-by: cache-ams2100141-AMS, cache-lga21944-LGA, cache-lga21959-LGA, cache-lga21959-LGA
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback