chastity.com.br 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

0High

7Medium

4Low

2Info

Collected 15 hours ago13.5sfrom cache

Certificate Transparency21
DNS resolution15
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs38
Registration
DNS posture2
Email authentication2
Certificate
Security headers2
Archived URLs
Analysis14

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.
note2 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

Shodan matched these CVEs against the service banners it saw on 142.44.136.51 (webmail.chastity.com.br), which advertise openssh 8.0, exim 4.99.2. 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-60002 CVE-2026-60001 CVE-2026-60000 CVE-2026-59999 CVE-2026-59998 CVE-2026-59997 CVE-2026-59996 CVE-2026-59995 CVE-2026-48840 CVE-2026-45185 CVE-2026-35414 CVE-2026-35388 CVE-2026-35387 ...and 15 more
What to do
Confirm the running versions on 142.44.136.51 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-60002 ↗CVE-2026-60001 ↗CVE-2026-60000 ↗
asset: 142.44.136.51
142.44.136.51 (webmail.chastity.com.br) reports openssh 8.0, exim 4.99.2. 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: 142.44.136.51
FTP transmits credentials in cleartext.
What to do
Restrict 21/tcp to a VPN, bastion, or allow-listed source range.
asset: 142.44.136.51: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: 142.44.136.51: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://www.chastity.com.br/
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.chastity.com.br/
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: chastity.com.br
Without clientTransferProhibited, a compromised registrar account can move the domain to another registrar in days, with no second step.
What to do
Enable the transfer lock (and registrar lock, if offered) in the registrar control panel.
asset: chastity.com.br
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 142.44.136.51:25
Browsers and the preload list expect at least six months; shorter values give little protection between visits.
What to do
Raise max-age to 31536000 (one year).
asset: https://www.chastity.com.br/
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.chastity.com.br/
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: chastity.com.br
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: chastity.com.br
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: chastity.com.br

final https://www.chastity.com.br/status 200time 2000msstack cloudflare · WordPress 7.0.4

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

✓Receives mail via 1 server
mail.chastity.com.br
!SPFends in ~all
v=spf1 a mx ip4:51.81.242.83 include:relay.mailbaby.net ~all
!DMARCp=none
v=DMARC1; p=none; rua=mailto:rua@dmarc.brevo.com
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
✓IPv6 (AAAA)
✓2 nameservers
amos.ns.cloudflare.com aspen.ns.cloudflare.com

✓Registered with NEWFOLD8.3 years old
chastity.com.br
✓Registration expiry246 days
2027-05-11
✗Transfer lock
none
✓2 nameservers at registry
amos.ns.cloudflare.com aspen.ns.cloudflare.com

Address	Ports	CVEs	Edge	Network
172.67.179.151 www.chastity.com.br +3	80443205220532082208320862087+5	0	Cloudflare~	—
104.21.31.189 www.chastity.com.br +5	80443205220532082208320862087+5	0	Cloudflare~	—
142.44.136.51 webmail.chastity.com.br +6	2122255380110143443+4	30	direct	—

Archived URLs

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

chastity.com.br security report

Critical

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames