Grade A — 5 minor.
passive scan · the deep checks need you signed in · scanned 3h ago
This is a passive website security report for tuback.link, graded A (90/100). We checked its SSL certificate, HTTP security headers, DNS records, email spoofing protection and publicly exposed files — the same surface a browser and a search engine already see.
We found 5 issues on this scan — each has a plain-English explanation and a copy-paste fix below.
Not your site? Get the same free report for yours →
You have a Content-Security-Policy, which is great — but it contains a wildcard source or allows 'unsafe-inline'/'unsafe-eval' in script-src. Those let injected scripts execute, which is most of what a CSP is meant to stop.
Your responses advertise the exact software you run (X-Powered-By: Next.js). It's not a hole by itself, but it hands attackers a shortcut: they can look up known vulnerabilities for that precise version instead of probing blindly.
The DMARC record on tuback.link uses p=none, which only reports spoofing — it doesn't stop it. Forged mail claiming to be from your domain is still delivered.
tuback.link is not protected by DNSSEC. DNSSEC signs your DNS records so resolvers can detect a forged answer — without it, an attacker who can poison DNS could point your domain at their own server without touching anything you control.
tuback.link publishes no CAA records. CAA tells the world which certificate authorities are allowed to issue HTTPS certificates for your domain. Without it, any CA can be persuaded to issue a cert for your domain, which widens the door to mis-issuance.
Sign up to fix these — then run the checks a passive scan can't. The stuff that actually gets vibe-coded apps hacked:
free for your first app · no card
Not tuback.link? Scan your own site free →