mosu-mvd.com security report

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

79risk

Critical

Exposed services or known CVEs need attention now.

1Critical

1High

4Medium

4Low

1Info

Collected 17 hours ago46.9sfrom cache

Certificate Transparency2
DNS resolution2
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs8
Registration
DNS posture2
Email authentication0
Certificate
Security headers1
Archived URLs
Analysis11

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 109.95.210.220 (mosu-mvd.com), which advertise exim 4.97.1. 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 CVE-2026-48840 CVE-2026-45185 CVE-2026-40687 CVE-2026-40686 CVE-2026-40685 CVE-2026-40684 CVE-2025-67896 CVE-2025-30232 CVE-2024-39929
What to do
Confirm the running versions on 109.95.210.220 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-66141 ↗CVE-2026-66140 ↗CVE-2026-48840 ↗CVE-2026-45185 ↗CVE-2026-40687 ↗
asset: 109.95.210.220
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.mosu-mvd.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@mosu-mvd.com"`, review the reports, then move to p=quarantine and p=reject.
asset: mosu-mvd.com
109.95.210.220 (mosu-mvd.com) reports exim 4.97.1. 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: 109.95.210.220
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://mosu-mvd.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://mosu-mvd.com/
Nothing tells receiving mail servers which hosts may send as @mosu-mvd.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: mosu-mvd.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://mosu-mvd.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://mosu-mvd.com/
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://mosu-mvd.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: mosu-mvd.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: mosu-mvd.com

final https://mosu-mvd.com/status 200time 1457msstack cloudflare · PHP/8.1.34

✓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

–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
ns1.reg.ru ns2.reg.ru

✓Registered with Registrar of Domain Names REG.RU LLC22.3 years old
mosu-mvd.com
✓Registration expiry256 days
2027-05-21
✓Transfer lock
client transfer prohibited
✓2 nameservers at registry
ns1.reg.ru ns2.reg.ru

Address	Ports	CVEs	Edge	Network
109.95.210.220 mosu-mvd.com +2	8011014346558799388888889	11	direct	—

Archived URLs

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

mosu-mvd.com security report

Critical

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames