shrink4menforum.com security report

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

87risk

Critical

Exposed services or known CVEs need attention now.

1Critical

2High

6Medium

6Low

1Info

Collected 19 hours ago50.5sfrom cache

Certificate Transparency
DNS resolution1
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs6
Registration
DNS posture2
Email authentication0
Certificate
Security headers1
Archived URLs
Analysis16

noteCertificate Transparency did not complete (HTTP 502). 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.

Shodan matched these CVEs against the service banners it saw on 107.180.113.32 (shrink4menforum.com), which advertise openssh 8.0, mariadb 10.11.18-MariaDB-cll-lve, exim 4.99.5. 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-26465 CVE-2023-51767 ...and 11 more
What to do
Confirm the running versions on 107.180.113.32 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: 107.180.113.32
Database engines should sit behind a private network.
What to do
Restrict 3306/tcp to a VPN, bastion, or allow-listed source range.
asset: 107.180.113.32: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.shrink4menforum.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@shrink4menforum.com"`, review the reports, then move to p=quarantine and p=reject.
asset: shrink4menforum.com
107.180.113.32 (shrink4menforum.com) reports openssh 8.0, mariadb 10.11.18-MariaDB-cll-lve, exim 4.99.5. 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: 107.180.113.32
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: 107.180.113.32: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://www.shrink4menforum.com/activity.php?s=d0af26205836a327dfa5aa550ebad285
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://www.shrink4menforum.com/activity.php?s=d0af26205836a327dfa5aa550ebad285
The browser will also send this cookie over plain http://, where it can be captured.
What to do
Add `Secure` to the cookie.
asset: https://www.shrink4menforum.com/activity.php?s=d0af26205836a327dfa5aa550ebad285
Nothing tells receiving mail servers which hosts may send as @shrink4menforum.com, so anyone can. Even a domain that sends no mail should say so, or it becomes a free spoofing target.
What to do
Publish `v=spf1 -all` to state that this domain sends no mail.
asset: shrink4menforum.com
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.shrink4menforum.com/activity.php?s=d0af26205836a327dfa5aa550ebad285
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.shrink4menforum.com/activity.php?s=d0af26205836a327dfa5aa550ebad285
Exact versions in response headers let anyone match the server against a CVE feed without touching it.
What to do
Strip version tokens (`ServerTokens Prod`, `server_tokens off`, remove X-Powered-By).
asset: https://www.shrink4menforum.com/activity.php?s=d0af26205836a327dfa5aa550ebad285
Without HttpOnly, any injected script can read and exfiltrate this cookie.
What to do
Add `HttpOnly` unless client-side code genuinely needs to read it.
asset: https://www.shrink4menforum.com/activity.php?s=d0af26205836a327dfa5aa550ebad285
Without HttpOnly, any injected script can read and exfiltrate this cookie.
What to do
Add `HttpOnly` unless client-side code genuinely needs to read it.
asset: https://www.shrink4menforum.com/activity.php?s=d0af26205836a327dfa5aa550ebad285
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: shrink4menforum.com
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: shrink4menforum.com

final https://www.shrink4menforum.com/activity.php?s=d0af26205836a327dfa5aa550ebad285status 200time 1736msstack cloudflare · PHP/7.4.33 · vBulletin 4.2.2

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

✗Cookie bb23_sessionhash
no Secure · HttpOnly · no SameSite
!Cookie bb23_lastvisit
Secure · no HttpOnly · no SameSite
!Cookie bb23_lastactivity
Secure · no HttpOnly · no SameSite

–No MX records — domain does not receive mail
✗SPF
no record
✗DMARC
no record
–MTA-STSn/a

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓2 nameservers
ns05.domaincontrol.com ns06.domaincontrol.com

✓Registered with GoDaddy.com, LLC15.9 years old
shrink4menforum.com
✓Registration expiry402 days
2027-10-14
✓Transfer lock
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
✓2 nameservers at registry
ns05.domaincontrol.com ns06.domaincontrol.com

Address	Ports	CVEs	Edge	Network
107.180.113.32 shrink4menforum.com +2	22801434434653306	26	direct	—

Archived URLs

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

shrink4menforum.com security report

Critical

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames