chatslang.com security report

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

45risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

1High

2Medium

3Low

2Info

Collected 7 hours ago69.2sfrom cache

Certificate Transparency8
DNS resolution8
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs3
Registration
DNS posture2
Email authentication1
Certificate
Security headers1
Archived URLs
Analysis8

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.

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.chatslang.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@chatslang.com"`, review the reports, then move to p=quarantine and p=reject.
asset: chatslang.com
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://slang.net/
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://slang.net/
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://slang.net/
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://slang.net/
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: chatslang.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: chatslang.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: chatslang.com

final https://slang.net/status 200time 1542msstack cloudflare

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

✓Receives mail via 1 server
chatslang.com
!SPFends in ~all
v=spf1 ip4:67.43.14.72 +a +mx +ip4:67.43.14.73 +ip4:67.43.14.80 +ip4:67.225.166.120 ~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.sharpened.com ns2.sharpened.com

✓Registered with GoDaddy.com, LLC24.9 years old
chatslang.com
✓Registration expiry413 days
2027-10-25
✓Transfer lock
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
✓2 nameservers at registry
ns1.sharpened.com ns2.sharpened.com

Address	Ports	CVEs	Edge	Network
67.43.14.72 webmail.chatslang.com +8	80110443	0	direct	—

Archived URLs

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

chatslang.com security report

Moderate

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames