mb-zip.com 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.

1Critical

1High

6Medium

6Low

2Info

Collected 5 hours ago18.3sfrom cache

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

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.

Shodan matched these CVEs against the service banners it saw on 194.58.88.142 (mb-zip.com), which advertise openssh 8.9p1, exim 4.95, nginx 1.18.0. 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-48840 CVE-2026-40687 CVE-2026-40686 CVE-2026-40685 CVE-2026-40684 CVE-2025-67896 CVE-2025-23419 CVE-2024-39929 CVE-2023-51766 CVE-2023-44487 CVE-2023-42119 CVE-2023-42117 CVE-2023-42116 CVE-2023-42115 CVE-2023-42114 ...and 5 more
What to do
Confirm the running versions on 194.58.88.142 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-48840 ↗CVE-2026-40687 ↗CVE-2026-40686 ↗CVE-2026-40685 ↗CVE-2026-40684 ↗
asset: 194.58.88.142
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.mb-zip.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@mb-zip.com"`, review the reports, then move to p=quarantine and p=reject.
asset: mb-zip.com
194.58.88.142 (mb-zip.com) reports openssh 8.9p1, exim 4.95, nginx 1.18.0. 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: 194.58.88.142
FTP transmits credentials in cleartext.
What to do
Restrict 21/tcp to a VPN, bastion, or allow-listed source range.
asset: 194.58.88.142: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: 194.58.88.142:22
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://mb-zip.com/
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://mb-zip.com/
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://mb-zip.com/
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 194.58.88.142:25
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://mb-zip.com/
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://mb-zip.com/
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://mb-zip.com/
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: mb-zip.com
Not urgent, but worth confirming auto-renew is on and the card on file is current.
What to do
Check auto-renew.
asset: mb-zip.com
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: mb-zip.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: mb-zip.com

final https://mb-zip.com/status 200time 1434msstack cloudflare

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

✗Cookie PHPSESSID
no Secure · no HttpOnly · no SameSite

✓Receives mail via 2 servers
mail.mb-zip.com mail.mb-zip.com
!SPFends in ~all
v=spf1 ip4:148.251.7.50 a mx ~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
ns1.mb-zip.com ns2.mb-zip.com

✓Registered with Regional Network Information Center, JSC dba RU-CENTER13.8 years old
mb-zip.com
!Registration expiry74 days
2026-11-20
✓Transfer lock
client transfer prohibited
✓2 nameservers at registry
ns1.mb-zip.com ns2.mb-zip.com

Address	Ports	CVEs	Edge	Network
194.58.88.142 mb-zip.com	2122255380111143443+1	20	direct	—

Archived URLs

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

mb-zip.com security report

Critical

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames