sexsiterus.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

2High

4Medium

2Low

2Info

Collected 10 hours ago4.6sfrom cache

Certificate Transparency
DNS resolution1
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs7
Registration
DNS posture2
Email authentication1
Certificate
Security headers2
Archived URLs
Analysis11

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 5.61.54.213 (sexsiterus.com), which advertise openssh 8.0, nginx 1.14.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-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-2025-23419 ...and 20 more
What to do
Confirm the running versions on 5.61.54.213 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: 5.61.54.213
A visitor who types the address without https, or follows an old link, gets the unencrypted site. On public Wi-Fi that page can be read and rewritten in transit.
What to do
Redirect every http:// request to https:// with a 301, then add HSTS.
asset: https://sexsiterus.com/
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.sexsiterus.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@sexsiterus.com"`, review the reports, then move to p=quarantine and p=reject.
asset: sexsiterus.com
5.61.54.213 (sexsiterus.com) reports openssh 8.0, nginx 1.14.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: 5.61.54.213
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: 5.61.54.213: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://sexsiterus.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://sexsiterus.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://sexsiterus.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: sexsiterus.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: sexsiterus.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: sexsiterus.com

final https://sexsiterus.com/status 526time 706msstack cloudflare

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

✓Receives mail via 1 server
mail.sexsiterus.com
!SPFends in ~all
v=spf1 ip4:5.61.52.82 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.dnsdomen.com ns2.dnsdomen.com

✓Registered with NameSilo, LLC8.7 years old
sexsiterus.com
✓Registration expiry105 days
2026-12-21
✓Transfer lock
client transfer prohibited
✓2 nameservers at registry
ns1.sexsiterus.com ns2.sexsiterus.com

Address	Ports	CVEs	Edge	Network
5.61.54.213 sexsiterus.com	22538011099399510050	35	direct	—

Archived URLs

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

sexsiterus.com security report

Critical

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames