cultureforum.net security report

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

91risk

Critical

Exposed services or known CVEs need attention now.

2Critical

2High

8Medium

3Low

2Info

Collected 4 hours ago18.6sfrom cache

Certificate Transparency80
DNS resolution11
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs20
Registration
DNS posture2
Email authentication1
Certificate
Security headers0
Archived URLs
Analysis17

noteFound 80 hostnames; this runtime allows 50 outbound requests per scan, so the 21 most likely to matter were resolved.
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.

Shodan matched these CVEs against the service banners it saw on 192.232.249.155 (mail.cultureforum.net), which advertise exim 4.99.5, openssh 9.9, mysql 5.7.44-48. 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-60002 CVE-2026-60001 CVE-2026-60000 CVE-2026-59999 CVE-2026-59998 CVE-2026-59997 CVE-2026-59996 CVE-2026-59995 CVE-2026-35414 CVE-2026-35388 CVE-2026-35387 CVE-2026-35385 CVE-2025-32728 CVE-2025-26466 CVE-2025-26465 ...and 3 more
What to do
Confirm the running versions on 192.232.249.155 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-60002 ↗CVE-2026-60001 ↗CVE-2026-60000 ↗CVE-2026-59999 ↗CVE-2026-59998 ↗
asset: 192.232.249.155
Shodan matched these CVEs against the service banners it saw on 139.177.199.203 (cultureforum.net), which advertise openssh 8.2p1, http server 2.4.41. 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-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 84 more
What to do
Confirm the running versions on 139.177.199.203 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-49975 ↗CVE-2026-44631 ↗CVE-2026-44186 ↗CVE-2026-44185 ↗CVE-2026-44119 ↗
asset: 139.177.199.203
Database engines should sit behind a private network.
What to do
Restrict 3306/tcp to a VPN, bastion, or allow-listed source range.
asset: 192.232.249.155:3306
SPF and DKIM alone do not protect the From: address a person sees. Without DMARC, a spoofed message can pass SPF for some other domain and still display yours.
What to do
Publish `_dmarc.cultureforum.net TXT "v=DMARC1; p=none; rua=mailto:dmarc@cultureforum.net"`, review the reports, then move to p=quarantine and p=reject.
asset: cultureforum.net
192.232.249.155 (mail.cultureforum.net) reports exim 4.99.5, openssh 9.9, mysql 5.7.44-48. 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: 192.232.249.155
FTP transmits credentials in cleartext.
What to do
Restrict 21/tcp to a VPN, bastion, or allow-listed source range.
asset: 192.232.249.155:21
Public SSH invites credential stuffing and key brute force.
What to do
Restrict 22/tcp to a VPN, bastion, or allow-listed source range.
asset: 192.232.249.155:22
139.177.199.203 (cultureforum.net) reports openssh 8.2p1, http server 2.4.41. 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: 139.177.199.203
Public SSH invites credential stuffing and key brute force.
What to do
Restrict 22/tcp to a VPN, bastion, or allow-listed source range.
asset: 139.177.199.203:22
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://cultureforum.net/
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://cultureforum.net/
No X-Frame-Options or CSP frame-ancestors directive, so another site can load this page invisibly inside its own and trick users into clicking.
What to do
Send `X-Frame-Options: DENY` or `Content-Security-Policy: frame-ancestors ’none’`.
asset: https://cultureforum.net/
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://cultureforum.net/
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://cultureforum.net/
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: cultureforum.net
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: cultureforum.net
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: cultureforum.net

final https://cultureforum.net/status 200time 1382msstack cloudflare · WordPress 7.1

✓http:// redirects to https://
✗Strict-Transport-Security
✗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
mail.cultureforum.net
!SPFends in ~all
v=spf1 a mx include:websitewelcome.com ~all
✗DMARC
no record
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓2 nameservers
ns6101.hostgator.com ns6102.hostgator.com

✓Registered with GoDaddy.com, LLC21.5 years old
cultureforum.net
✓Registration expiry175 days
2027-03-01
✓Transfer lock
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
✓2 nameservers at registry
ns6101.hostgator.com ns6102.hostgator.com

Address	Ports	CVEs	Edge	Network
192.232.249.155 mail.cultureforum.net +10	2122265380110143443+9	18	direct	—
139.177.199.203 cultureforum.net +5	2280443	99	direct	—

Archived URLs

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

cultureforum.net security report

Critical

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames