Skip to content
https://commonslibrary.parliament.uk

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Madrid, Spain
403 Forbidden
Checks
9
5 PASS 4 REVIEW
B
DNS Records
2 A records, 40 ms lookup
REVIEW
2 A records, 40 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.17.177.119, 104.17.176.119
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700::6811:b177, 2606:4700::6811:b077
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: commonslibrary.parliament.uk.cdn.cloudflare.net
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'.
Info::
DNS resolution time: 40 ms
Got: 40 ms
A104.17.177.119, 104.17.176.119
AAAA2606:4700::6811:b177, 2606:4700::6811:b077
CNAMEcommonslibrary.parliament.uk.cdn.cloudflare.net
NS
MX
TXT
CAALookup not available with standard resolver
Resolved in 40 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

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)

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 403 Expected: 301 redirect to HTTPS

www / non-www

https://www.commonslibrary.parliament.uk/
200https://commonslibrary.parliament.uk/

HTTP → HTTPS

403http://commonslibrary.parliament.uk/

HTTP version does not redirect to HTTPS

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

Certificate validity

51
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: CDG)
Got: cf-ray: 9f0817051b627927-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9f0817051b627927-CDG
A+
Redirect Chain
0 redirect(s), 60 ms total
PASS
0 redirect(s), 60 ms total

https://commonslibrary.parliament.uk

60 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://commonslibrary.parliament.uk40360 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (16 ms)
PASS
IPv6 reachable (16 ms)
Info::
IPv6 is configured and reachable at 2606:4700::6811:b177, 2606:4700::6811:b077
Got: 16 ms connect
IPv6 Ready
AAAA Records 2606:4700::6811:b177, 2606:4700::6811:b077 Connection Reachable (16 ms)
A
Crawlability
no robots.txt, sitemap with 20 URLs
PASS
no robots.txt, sitemap with 20 URLs
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 20 entries
Info::
Sitemap index with 20 child sitemaps

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

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.

A+
Domain Intelligence
parliament.uk — via No registrar listed. This domain is directly registered with Nominet., hosted on AWS
PASS
parliament.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.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

Unknown

SSL certificate

51 days

Issued by Google Trust Services

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

34.242.126.108

Registrar

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

Lock status unknown 6 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 a1-34.akam.net, a2-65.akam.net, a7-64.akam.net, a9-65.akam.net, a18-64.akam.net, a20-65.akam.net
Registrant Parliament of the United Kingdom
Hosting
IP Address 34.242.126.108
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: whois (0.9s)
A+
HTTP Probe Timing
Total 115 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
48 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
17 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
25 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
115 ms
Total Time Total request time from DNS lookup through full response.
115 ms

Connection waterfall

DNS Lookup 48 ms TCP Connect 17 ms TLS Handshake 25 ms Server Processing 26 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