mano-security.com security report

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

77risk

Critical

Exposed services or known CVEs need attention now.

1Critical

0High

6Medium

4Low

2Info

Collected 11 hours ago5.1sfrom cache

Certificate Transparency1
DNS resolution1
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs13
Registration
DNS posture3
Email authentication2
Certificate
Security headers0
Archived URLs
Analysis13

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 185.205.184.115 (mano-security.com), which advertise proftpd 1.3.5a, jquery 3.4.1, http server 2.4.18. 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-63091 CVE-2026-63090 CVE-2026-53994 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-42167 CVE-2026-35025 CVE-2026-34356 CVE-2026-34355 ...and 119 more
What to do
Confirm the running versions on 185.205.184.115 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-63091 ↗CVE-2026-63090 ↗CVE-2026-53994 ↗CVE-2026-49975 ↗CVE-2026-44631 ↗
asset: 185.205.184.115
185.205.184.115 (mano-security.com) reports proftpd 1.3.5a, jquery 3.4.1, http server 2.4.18. 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: 185.205.184.115
FTP transmits credentials in cleartext.
What to do
Restrict 21/tcp to a VPN, bastion, or allow-listed source range.
asset: 185.205.184.115:21
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://ms-security-ltd.com/
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://ms-security-ltd.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://ms-security-ltd.com/
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: mano-security.com
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 185.205.184.115: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://ms-security-ltd.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://ms-security-ltd.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: mano-security.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: mano-security.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: mano-security.com

final https://ms-security-ltd.com/status 200time 3923msstack 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
manosecurity-com01b.mail.eo.outlook.com
✓SPFends in -all
v=spf1 include:spf.protection.outlook.com -all
!DMARCp=none
v=DMARC1; p=none; rua=mailto:it_notifications@mano-security.com; ruf=mailto:it_notifications@mano-security.com; fo=1
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓3 nameservers
dns1.cl8.com dns2.cl8.com dns3.cl8.com

✓Registered with PDR Ltd. d/b/a PublicDomainRegistry.com22.3 years old
mano-security.com
✓Registration expiry245 days
2027-05-10
✓Transfer lock
client transfer prohibited
✓3 nameservers at registry
dns1.cl8.com dns2.cl8.com dns3.cl8.com

Address	Ports	CVEs	Edge	Network
185.205.184.115 mano-security.com	21255380110143443465+5	134	direct	—

Archived URLs

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

mano-security.com security report

Critical

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames