ogl.co.uk security report

Certificate, security headers, email authentication, DNS, registration, and exposed hosts — from public sources.

66risk

Elevated

Several issues worth triaging this week.

0Critical

3High

4Medium

8Low

2Info

Collected 11 hours ago7.4sfrom cache

Domain—

unavailable

Certificate Transparency11
DNS resolution13
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs75
Registration
DNS posture2
Email authentication2
Certificate
Security headers3
Archived URLs
Analysis17

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.
noteRegistration did not complete (HTTP 429). Results below are partial.
note5 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

Shodan matched these CVEs against the service banners it saw on 97.107.135.178 (link.ogl.co.uk), which advertise exim 4.99.4. These are version-fingerprint matches, not confirmed exploits: a distribution may have back-ported the fix while leaving the banner unchanged. Severity reflects the volume of known issues associated with this host, not a CVSS score. CVE-2026-66141 CVE-2026-66140
What to do
Confirm the running versions on 97.107.135.178 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-66141 ↗CVE-2026-66140 ↗
asset: 97.107.135.178
Shodan matched these CVEs against the service banners it saw on 170.187.131.209 (link.ogl.co.uk), which advertise exim 4.99.4. These are version-fingerprint matches, not confirmed exploits: a distribution may have back-ported the fix while leaving the banner unchanged. Severity reflects the volume of known issues associated with this host, not a CVSS score. CVE-2026-66141 CVE-2026-66140
What to do
Confirm the running versions on 170.187.131.209 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-66141 ↗CVE-2026-66140 ↗
asset: 170.187.131.209
Shodan matched these CVEs against the service banners it saw on 185.3.93.228 (link.ogl.co.uk), which advertise exim 4.99.4. These are version-fingerprint matches, not confirmed exploits: a distribution may have back-ported the fix while leaving the banner unchanged. Severity reflects the volume of known issues associated with this host, not a CVSS score. CVE-2026-66141 CVE-2026-66140
What to do
Confirm the running versions on 185.3.93.228 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-66141 ↗CVE-2026-66140 ↗
asset: 185.3.93.228
97.107.135.178 (link.ogl.co.uk) reports exim 4.99.4. Publishing precise versions lets anyone match the host against a CVE feed without probing it, which is how targets get shortlisted for mass exploitation after a new advisory lands.
What to do
Suppress version tokens in server banners (for example `ServerTokens Prod` in Apache) and keep the packages current.
asset: 97.107.135.178
170.187.131.209 (link.ogl.co.uk) reports exim 4.99.4. Publishing precise versions lets anyone match the host against a CVE feed without probing it, which is how targets get shortlisted for mass exploitation after a new advisory lands.
What to do
Suppress version tokens in server banners (for example `ServerTokens Prod` in Apache) and keep the packages current.
asset: 170.187.131.209
185.3.93.228 (link.ogl.co.uk) reports exim 4.99.4. Publishing precise versions lets anyone match the host against a CVE feed without probing it, which is how targets get shortlisted for mass exploitation after a new advisory lands.
What to do
Suppress version tokens in server banners (for example `ServerTokens Prod` in Apache) and keep the packages current.
asset: 185.3.93.228
Receivers are asked to report spoofing but not to block it. This is the right first step, and the wrong place to stop.
What to do
Once reports look clean, move to p=quarantine, then p=reject.
asset: ogl.co.uk
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 97.107.135.178:25
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 170.187.131.209:25
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 185.3.93.228:25
oglint-sr-test.ad.ogl.co.uk appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: oglint-sr-test.ad.ogl.co.uk
www.oglint-sr-test.ad.ogl.co.uk appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: www.oglint-sr-test.ad.ogl.co.uk
Lets browsers guess content types, which turns some upload and text endpoints into script injection points.
What to do
Send `X-Content-Type-Options: nosniff` on every response.
asset: https://www.ogl.co.uk/
Full URLs — including any tokens or IDs in them — are sent to every third party the page links to.
What to do
Send `Referrer-Policy: strict-origin-when-cross-origin`.
asset: https://www.ogl.co.uk/
Answers for this domain are not signed, so a resolver cannot tell a forged response from a real one.
What to do
Enable DNSSEC at your DNS host and publish the DS record at the registrar.
asset: ogl.co.uk
Mail to this domain can be downgraded to plaintext by an on-path attacker, because senders have no way to know TLS is required.
What to do
Publish an MTA-STS policy (a TXT record plus a small HTTPS-hosted file).
asset: ogl.co.uk
Any public certificate authority may issue certificates for this domain. CAA lets you name the ones allowed to.
What to do
Add a CAA record naming your CA, e.g. `0 issue "letsencrypt.org"`.
asset: ogl.co.uk

final https://www.ogl.co.uk/status 200time 639msstack cloudflare

✓http:// redirects to https://
✓Strict-Transport-Security
max-age=31536000
✓Content-Security-Policy
frame-ancestors 'self'
✓Clickjacking protection
SAMEORIGIN
✗X-Content-Type-Options
✗Referrer-Policy
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✓Cookie _cfuvid
Secure · HttpOnly · SameSite=none

✓Receives mail via 1 server
ogl-co-uk.mail.protection.outlook.com
!SPFends in ~all
v=spf1 mx include:spf.protection.outlook.com include:spf.exclaimer.net ip4:185.120.72.0/22 ip4:188.39.129.96/29 ip4:37.200.113.130 ip4:195.110.84.130 ~all
!DMARCp=none
v=DMARC1; p=none
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓2 nameservers
lewis.ns.cloudflare.com luciane.ns.cloudflare.com

Address	Ports	CVEs	Edge	Network
198.202.211.1 ogl.co.uk +3	80443205220532082208320862087+5	0	Cloudflare~	—
172.67.198.187 blog.ogl.co.uk +3	80443205220532082208320862087+5	0	Cloudflare~	—
104.21.44.106 blog.ogl.co.uk +3	80443205220532082208320862087+5	0	Cloudflare~	—
162.159.140.128 notification.ogl.co.uk +2	80443205220532082208320862087+5	0	Cloudflare~	—
172.66.0.126 notification.ogl.co.uk +2	80443205220532082208320862087+5	0	Cloudflare~	—
97.107.135.178 link.ogl.co.uk +4	258044310256	2	direct	—
170.187.131.209 link.ogl.co.uk +4	2580443	2	direct	—
185.3.93.228 link.ogl.co.uk +3	2580443	2	direct	—

Archived URLs

Endpoints the Wayback Machine has kept — config files, backups, scripts. Slow to fetch, so it is here on request.

ogl.co.uk security report

Elevated

Findings

Security headers

Email authentication

DNS

Hosts

Hostnames