Skip to content
https://yougov.co.uk

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from New York, United Stated
301 Moved Permanently
Checks
9
4 PASS 4 REVIEW 1 FIX
D
TLS Certificate Expiry & Recommendations
Action
3 days until leaf cert expires — 5 issues to address
FIX

Certificate validity

3
days left
0d 30d 60d 90d+
Renew urgently — under 14 days remaining

Recommended actions

  • Renew certificate — 3 days remaining
  • 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
B
Redirect Chain
1 redirect(s), 1323 ms total
REVIEW
1 redirect(s), 1323 ms total
Info::
Single redirect
Got: https://yougov.co.uk → https://yougov.com/en-gb/ (301)
Warning::
Redirect overhead: 1323 ms total
Got: 1323 ms
Info::
Cross-domain redirect detected

https://yougov.co.uk

219 ms · HTTP/1.1

301

https://yougov.com/en-gb/

1105 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://yougov.co.uk301219 msHTTP/1.1
2https://yougov.com/en-gb/2001105 msHTTP/1.1istio-envoy

See the visual redirect chain in the HTTP Probe tab →

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
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

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

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

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.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
CDN & Delivery
Incapsula
REVIEW
Incapsula
Info::
Site is served via Incapsula CDN
Got: x-iinfo: 5-9462403-9462405 NNNN CT(192 360 0) RT(1776894329529 11) q(0 0 6 0) r(7 8) U24
CDN Detected: Incapsula
Provider Incapsula Evidence x-iinfo: 5-9462403-9462405 NNNN CT(192 360 0) RT(1776894329529 11) q(0 0 6 0) r(7 8) U24
A+
DNS Records
2 A records, 77 ms lookup
PASS
2 A records, 77 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 45.60.76.62, 45.60.85.62
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1224.awsdns-25.org, ns-1742.awsdns-25.co.uk, ns-289.awsdns-36.com, ns-784.awsdns-34.net
Info::
1 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: 77 ms
Got: 77 ms
A45.60.76.62, 45.60.85.62
AAAA
CNAME
NSns-1224.awsdns-25.org, ns-1742.awsdns-25.co.uk, ns-289.awsdns-36.com, ns-784.awsdns-34.net
MX
0 yougov-co-uk.mail.protection.outlook.com
TXT
MS=ms89773984
_globalsign-domain-verification=dBOzFhERBMudZtUSjDA0qh4NwjO5RHFstllPZIOMbR
SPF v=spf1 include:spf-a.outlook.com include:spf-b.outlook.com include:spf-c.outlook...
CAALookup not available with standard resolver
Resolved in 77 ms

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+
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: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.yougov.co.uk/
200https://yougov.co.uk/

Preferred variant: non-www

HTTP → HTTPS

301http://yougov.co.uk/ https://yougov.co.uk/

Consistent

A+
Domain Intelligence
yougov.co.uk — via CSC Corporate Domains, Inc, 26 years, 6 months old, hosted on INCAPSULA - Incapsula Inc, US
PASS
yougov.co.uk — via CSC Corporate Domains, Inc, 26 years, 6 months old, hosted on INCAPSULA - Incapsula Inc, US
Info::
Domain registered until Feb 19, 2028 (1 years, 10 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: CSC Corporate Domains, Inc
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: INCAPSULA - Incapsula Inc, US
Got: AS19551
Domain expiry

616 days

February 19, 2028

SSL certificate

3 days

Issued by GlobalSign nv-sa

Domain age

26 years, 6 months

Registered February 19, 2000

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

INCAPSULA - Incapsula Inc, US

ASN AS19551

45.60.76.62

Registrar

CSC Corporate Domains, Inc

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the TLS certificate or verify auto-renewal is working
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar CSC Corporate Domains, Inc
Created February 19, 2000 (26 years, 6 months ago)
Expires February 19, 2028 (1 years, 10 months)
Last Updated February 16, 2026
Name Servers ns-1224.awsdns-25.org., ns-1742.awsdns-25.co.uk., ns-289.awsdns-36.com., ns-784.awsdns-34.net.
DNSSEC Not enabled
Hosting
IP Address 45.60.76.62
ASN AS19551 (INCAPSULA - Incapsula Inc, US)
Provider INCAPSULA - Incapsula Inc, US
Data source: rdap (0.5s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

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

Connection waterfall

DNS Lookup 7 ms TCP Connect 6 ms TLS Handshake 9 ms Server Processing 746 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