Loading…
Loading…
Check the security settings anyone can see from outside: HTTPS and the SSL certificate, security headers, cookie flags, information leaks and whether your domain is protected against email spoofing.
The page is fetched once by our server; DNS records are read through public DNS. Nothing is stored.
Enter a website address or domain.
Our server visits the page once, like a normal browser, and reads the certificate and response headers. Your browser reads the domain’s public DNS records.
Each check gets a pass, warning or issue, with copy-paste fixes for Nginx, Apache, Cloudflare and Next.js.
HTTPS, http→https redirect, certificate validity, issuer, days until expiry and TLS version.
HSTS, Content-Security-Policy, X-Frame-Options or frame-ancestors, X-Content-Type-Options, Referrer-Policy and Permissions-Policy.
Secure, HttpOnly and SameSite flags on cookies, plus server and framework version headers that reveal too much.
SPF, DMARC policy, DKIM on common selectors, MX records, CAA and DNSSEC.
Yes. It only reads what any visitor or mail server can already see, with a single normal request.
Your domain is used for both. Without SPF and DMARC, criminals can send email that appears to come from your business.
Start with HTTPS, then DMARC and SPF, then HSTS and the other headers. Each finding includes the exact setting to add.
No. It means the visible basics are configured well. Security also depends on updates, passwords, backups and access control.
Audit any public page for technical SEO, content, schema, local SEO and AI search readiness, with a score and a fix for every issue.
Open toolGet keyword ideas grouped by intent, build a content brief and AI writing prompt, then score your draft for SEO, AEO and GEO.
Open toolTurn a rough idea into a structured prompt tuned for ChatGPT, Claude, Gemini, image, video, coding or n8n tools, with a quality score.
Open toolWe harden websites, set up SPF, DKIM and DMARC, and handle hosting for small businesses.