Grade D — 5 to fix, 3 minor.
passive scan · the deep checks need you signed in · scanned 1d ago
This is a passive website security report for cli.masoko.net, graded D (59/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 8 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 →
Your site is served over HTTPS but doesn't send a Strict-Transport-Security header. Without it, the first visit (or a link typed as http://) can be intercepted and downgraded to plain HTTP before the redirect happens — a foothold for man-in-the-middle attacks on public Wi-Fi.
There's no Content-Security-Policy header. A CSP is the single most effective defense against cross-site scripting (XSS): it tells the browser which sources of scripts, styles, and other content are allowed, so an injected <script> from a compromised dependency or a reflected input simply won't run.
Nothing stops your site from being embedded in an <iframe> on another domain. An attacker can overlay an invisible frame of your app on their page and trick a logged-in user into clicking buttons they can't see — a clickjacking attack.
Without `X-Content-Type-Options: nosniff`, browsers may guess ("sniff") the type of a response and, for example, run an uploaded file as JavaScript. It's a one-line header that closes a whole class of content-type confusion bugs.
The domain masoko.net publishes no SPF record. SPF is the DNS record that lists which mail servers are allowed to send email as your domain. Without it, spam filters have no way to tell your real mail from a forgery, and messages you do send are more likely to land in spam.
The domain masoko.net publishes no DMARC record. DMARC is what tells receiving mail servers to reject or quarantine messages that fail your SPF/DKIM checks. Without it, an attacker can send phishing emails with a "From:" address at your domain and inboxes have no signal to distrust them — a favourite trick for invoice fraud and credential phishing.
masoko.net 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.
masoko.net 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 cli.masoko.net? Scan your own site free →