thepaysites.com security report

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

54risk

Elevated

Several issues worth triaging this week.

0Critical

1High

4Medium

2Low

2Info

Collected 6 hours ago1.7sfrom cache

Certificate Transparency1
DNS resolution2
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs2
Registration
DNS posture2
Email authentication2
Certificate
Security headers2
Archived URLs
Analysis9

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.

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://thepaysites.com/
FTP transmits credentials in cleartext.
What to do
Restrict 21/tcp to a VPN, bastion, or allow-listed source range.
asset: 80.82.65.110: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://thepaysites.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://thepaysites.com/
The record ends in no all mechanism, so a spoofed message is neither passed nor failed and most receivers let it through.
What to do
End the record with -all (or ~all while you validate your senders).
asset: thepaysites.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://thepaysites.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: thepaysites.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: thepaysites.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: thepaysites.com

final https://thepaysites.com/status 526time 835msstack 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.fucking-cash.com
!SPF
v=spf1 redirect=fucking-cash.com
✓DMARCp=reject
v=DMARC1; p=reject
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓2 nameservers
ns1.thepaysites.com ns2.thepaysites.com

✓Registered with Moniker Online Services LLC20.4 years old
thepaysites.com
✓Registration expiry215 days
2027-04-10
✓Transfer lock
client transfer prohibited
✓4 nameservers at registry
ns1.moneycult.com ns1.thepaysites.com ns2.moneycult.com ns2.thepaysites.com

Address	Ports	CVEs	Edge	Network
80.82.65.110 thepaysites.com +2	2180	0	direct	—

Archived URLs

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

thepaysites.com security report

Elevated

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames