ocean.gov.za security report

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

83risk

Critical

Exposed services or known CVEs need attention now.

2Critical

0High

5Medium

3Low

2Info

Collected 5 hours ago9.4sfrom cache

Certificate Transparency16
DNS resolution21
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs24
Registration
DNS posture2
Email authentication2
Certificate
Security headers2
Archived URLs
Analysis12

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.
noteNo registration data: RDAP has no record at this level.
note2 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 154.114.12.11 (ocean.gov.za), which advertise http server 2.4.57, php 8.3.13, openssl 3.0.7. 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-49975 CVE-2026-48913 CVE-2026-45447 CVE-2026-45446 CVE-2026-45445 CVE-2026-44631 CVE-2026-44186 CVE-2026-44185 CVE-2026-44119 CVE-2026-43951 CVE-2026-42770 CVE-2026-42767 CVE-2026-42766 CVE-2026-42536 CVE-2026-42535 ...and 126 more
What to do
Confirm the running versions on 154.114.12.11 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-49975 ↗CVE-2026-48913 ↗CVE-2026-45447 ↗CVE-2026-45446 ↗CVE-2026-45445 ↗
asset: 154.114.12.11
Shodan matched these CVEs against the service banners it saw on 154.114.12.27 (repository.ocean.gov.za), which advertise http server 2.4.57. 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-48913 CVE-2026-44631 CVE-2026-44186 CVE-2026-44185 CVE-2026-44119 CVE-2026-43951 CVE-2026-42536 CVE-2026-42535 CVE-2026-34356 CVE-2026-34355 CVE-2026-34059 CVE-2026-34032 CVE-2026-33857 CVE-2026-33523 CVE-2026-33007 ...and 47 more
What to do
Confirm the running versions on 154.114.12.27 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-48913 ↗CVE-2026-44631 ↗CVE-2026-44186 ↗CVE-2026-44185 ↗CVE-2026-44119 ↗
asset: 154.114.12.27
154.114.12.11 (ocean.gov.za) reports http server 2.4.57, php 8.3.13, openssl 3.0.7. 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: 154.114.12.11
154.114.12.27 (repository.ocean.gov.za) reports http server 2.4.57. 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: 154.114.12.27
Without HSTS the browser will still try http:// first on a fresh visit, which is the window an on-path attacker uses.
What to do
Send `Strict-Transport-Security: max-age=31536000; includeSubDomains` once you are sure everything works over HTTPS.
asset: https://ocean.gov.za/
CSP is the main defence that limits what an injected script can do. Without it, any XSS bug is fully exploitable.
What to do
Start with a report-only policy, tighten it against the reports, then enforce.
asset: https://ocean.gov.za/
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: ocean.gov.za
vpn.ocean.gov.za 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: vpn.ocean.gov.za
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://ocean.gov.za/
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: ocean.gov.za
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: ocean.gov.za
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: ocean.gov.za

final https://ocean.gov.za/status 526time 1399msstack cloudflare

✓http:// redirects to https://
✗Strict-Transport-Security
✗Content-Security-Policy
✓Clickjacking protection
SAMEORIGIN
✗X-Content-Type-Options
✓Referrer-Policy
same-origin
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✓Receives mail via 1 server
mx.ocean.gov.za
!SPFends in ~all
v=spf1 ip4:154.114.12.5 ip4:154.114.12.55 ip4:154.114.12.20 ip4:154.114.12.120 include:ocean.gov.za ~all
!DMARCp=none
v=DMARC1; p=none;rua=mailto:c273387da6974522af83cd401762f194@dmarc-reports.cloudflare.net;ruf=mailto:systems@ocean.gov.za;fo=1;
!MTA-STSinbound mail can be downgraded to plaintext

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

Address	Ports	CVEs	Edge	Network
172.67.152.73 zabbix.ocean.gov.za +6	80443205220532082208320862087+3	0	Cloudflare~	—
104.21.12.118 zabbix.ocean.gov.za +6	80443208220832086208720968080+2	0	Cloudflare~	—
154.114.12.11 ocean.gov.za +2	80	141	direct	—
154.114.12.27 repository.ocean.gov.za	443	62	direct	—
154.114.12.17 sadco.ocean.gov.za	443	0	direct	—
154.114.12.5 mail.ocean.gov.za +1	none known	0	direct	—
154.114.12.120 vpn.ocean.gov.za	none known	0	direct	—
154.114.56.2 dr.ocean.gov.za	none known	0	direct	—
154.114.12.25 ftp.ocean.gov.za	none known	0	direct	—
154.114.12.20 calypso.ocean.gov.za	none known	0	direct	—

Archived URLs

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

ocean.gov.za security report

Critical

Findings

Security headers

Email authentication

DNS

Hosts

Hostnames