leics.gov.uk security report
Certificate, security headers, email authentication, DNS, registration, and exposed hosts — from public sources.
50risk
Elevated
Several issues worth triaging this week.
0Critical
1High
3Medium
3Low
2Info
Collected 20.0sfrom cache
- Certificate Transparency
- DNS resolution1
- Network ownership0
- CDN / WAF detection0
- Exposed ports & CVEs2
- Registration
- DNS posture4
- Email authentication2
- Certificate
- Security headers1
- Archived URLs
- Analysis9
- noteCertificate Transparency did not complete (HTTP 404). Results below are partial.
- noteCertificate inspection is unavailable in this runtime.
- noteNetwork ownership lookup is unavailable in this runtime; ASN and org are omitted.
- noteCDN/WAF detection is unavailable in this runtime.
final https://www.leicestershire.gov.uk/status 403time 2750msstack cloudflare
- ✗http:// redirects to https://
- ✓Strict-Transport-Securitymax-age=15768000
- ✗Content-Security-Policy
- ✗Clickjacking protection
- ✗X-Content-Type-Options
- ✗Referrer-Policy
- –Permissions-Policyoptional
- –security.txt publishedoptional — tells researchers where to report bugs
- ✓Receives mail via 1 server
- !SPFends in ~allv=spf1 include:spf_ip.leics.gov.uk include:amazonses.com include:spf.mailjet.com include:_spf.newzapp.co.uk include:spf_c.oraclecloud.com include:sendgrid.net a:mailer.postoffice-payout.co.uk ~all
- ✓DMARCp=quarantinev=DMARC1; p=quarantine; sp=reject; adkim=s; aspf=s; fo=1; rua=mailto:dmarc.reporting@leics.gov.uk; ruf=mailto:dmarc.reporting@leics.gov.uk
- !MTA-STSinbound mail can be downgraded to plaintext
- !DNSSECanswers can be forged
- –CAAany CA may issue
- –IPv6 (AAAA)IPv4 only
- ✓4 nameservers
- ✓Registered with Cloud Next Limited23.2 years old
- ✓Registration expiry285 days2027-06-19
- ✗Transfer locknone
- ✓4 nameservers at registry
| Address | Ports | CVEs | Edge | Network |
|---|---|---|---|---|
| 81.131.36.144 leics.gov.uk +2 | 80443 | 0 | direct | — |
Archived URLs
Endpoints the Wayback Machine has kept — config files, backups, scripts. Slow to fetch, so it is here on request.