followin.io security report

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

40risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

0High

4Medium

3Low

1Info

Collected 11 hours ago3.6sfrom cache

Certificate Transparency
DNS resolution2
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs4
Registration
DNS posture2
Email authentication2
Certificate
Security headers0
Archived URLs
Analysis8

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.
noteNo registration data: RDAP has no record at this level.

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://followin.io/
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://followin.io/
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://followin.io/
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: followin.io
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://followin.io/
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://followin.io/
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: followin.io
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: followin.io

final https://followin.io/status 429time 37msstack cloudflare

✓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 3 servers
mx1.larksuite.com mx2.larksuite.com mx3.larksuite.com
✓SPFends in -all
v=spf1 +include:spf.onlarksuite.com -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
✓CAA
0 issue "amazon.com" · 0 issue "letsencrypt.org" · 0 issue "pki.goog" · 0 issue "sectigo.com"
–IPv6 (AAAA)IPv4 only
✓2 nameservers
ns1.vercel-dns.com ns2.vercel-dns.com

Address	Ports	CVEs	Edge	Network
216.150.16.193 followin.io +3	80443	0	direct	—
216.150.1.129 followin.io +3	80443	0	direct	—

Archived URLs

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

followin.io security report

Moderate

Findings

Security headers

Email authentication

DNS

Hosts

Hostnames