Skip to content

Free website security checker

Find common security issues with your website, email and DNS. Get clear findings and practical steps to fix them.

Checks public settings. No login access needed. What happens to the domain you enter

Example report

example.com
  • 2 Medium
  • 1 Low
  • 43 passed

Also 2 informational.

  • HSTS is not enabledexample.comMedium

    https://example.com/ answered without a Strict-Transport-Security header.

    Next step

    Add Strict-Transport-Security: max-age=31536000; includeSubDomains to HTTPS responses once every subdomain serves HTTPS.

    View fix guide

  • Cookie set without the Secure flagexample.comMedium

    https://example.com/ sets the cookie session without the Secure attribute.

    Next step

    Add the Secure attribute to every cookie the site sets over HTTPS.

    View fix guide

  • DMARC is in monitoring modeexample.comLow

    The DMARC policy is p=none, which reports on failing mail but does not stop it.

    Next step

    Once reports show your legitimate mail passing, move to p=quarantine and then p=reject.

    View fix guide

Check the settings that are easy to miss

  • HTTPS and certificates

    Check certificate validity and TLS settings.

  • Email protection

    Review SPF, DKIM and DMARC records.

  • Security headers

    Find missing browser protections.

  • DNS configuration

    Check DNSSEC, CAA and common DNS issues.

Also reviews disclosed software and lists names from public certificate logs. DKIM is looked for at common selectors, so finding no key this way does not prove a domain has none, and names from certificate logs are listed, not checked.

Understand the issue and your next step

Each finding explains what we found, why it matters and what you can change. Start with the issues that need attention, then open the evidence when you want the detail.

  1. Enter your domain
  2. Review the findings
  3. Follow the fix guides
Example finding

HSTS is not enabledMedium

HTTPS responses do not include a Strict-Transport-Security header.

Strict-Transport-Security: not present

Common issues you can put right

  • HSTS is not enabledMedium

    Your site may use HTTPS without telling browsers to keep using it on future visits. Check your HTTPS setup before enabling HSTS.

    Read the fix guide

  • DMARC is in monitoring modeLow

    Your policy can help you understand who sends mail for your domain, but it does not ask receivers to quarantine or reject messages that fail DMARC. Review legitimate senders before changing enforcement.

    Read the fix guide

  • No Content Security PolicyLow

    A CSP tells browsers which sources your pages can load. Start by understanding what your site needs, then test a policy before enforcing it.

    Read the fix guide

  • No DMARC policyMedium

    No DMARC record was found at _dmarc for the domain.

    Read the fix guide

  • TLS 1.0 is enabledMedium

    The server accepted a TLS 1.0 connection.

    Read the fix guide

  • No CAA recordsLow

    The domain does not publish CAA records.

    Read the fix guide

  • Software version disclosed in headersLow

    Response headers reveal the exact version of server software.

    Read the fix guide

Keep watch after you've fixed it

Ironfang Security rechecks a verified domain every week or every day and tells you what changed: new findings, fixes and certificates nearing expiry.

Free during the preview. Domain verification required.

  1. NewIssue detected
  2. FixedConfirmed by recheck
  3. ReopenedDetected again

How the check works

  • DNS: address records, nameserver redundancy, CAA, DNSSEC and dangling CNAMEs.
  • Email authentication, from DNS only: SPF, DMARC, DKIM at common selectors, and whether a domain that sends no mail says so.
  • TLS on port 443: HTTPS availability, certificate trust, name and expiry, old protocol versions, TLS 1.3 support and weak cipher suites.
  • HTTP: the redirect to HTTPS, HSTS, Content-Security-Policy, X-Content-Type-Options, clickjacking protection, Referrer-Policy, Permissions-Policy, version disclosure, cookie attributes and security.txt.
  • Technology: software the home page discloses, and advertised versions that are end of life.
  • Certificate transparency: names under the domain in public certificate logs, listed and not contacted.

Reading a result

It is a domain security check in one pass. For a registrable domain such as example.org the web checks cover both example.org and www.example.org; for a subdomain, only that name.

Each check passes, raises a finding, is informational, or could not be completed. A finding carries a severity for its potential impact and a separate confidence for how strong the evidence is, and names the one thing to change. There is no overall grade or score.

A clean result means these automated, low-impact checks found nothing to report. It does not mean the site is secure: they read public configuration and do not test the application, its logins or services on other ports.

What it does not do

  • It does not check exposed services. Connecting to ports beyond the web ports runs only in the External Security Check, for a domain you have verified.
  • It checks the domain and its www. name. Other subdomains are listed from certificate transparency logs but not checked; enter one on its own to check it.
  • Web checks read the home page and /.well-known/security.txt. Other pages, anything behind a login and the application itself are not tested.
  • It is an automated external check that never attempts to exploit anything. It is not a penetration test, an audit or a certification.

What happens to the domain you enter

The check runs from Ironfang Security's published scanner address with the same low-impact limits as a scan. Nothing you enter is stored or logged. A result is reused for five minutes, and a certificate log search for an hour, so a repeat check is quick and the domain is not checked again.

Guides

A few things worth knowing

What does this check cover?
It checks public website, email and DNS settings. It does not test your application, its source code or anything behind a login.
Does a clean result mean my website is secure?
It means these checks found no issues to report. Other weaknesses may still exist, including in your application, accounts and other services.
Does it check every page and subdomain?
The web checks cover the home page on the domain and its www name, or the individual subdomain you enter. Names found in certificate logs are listed for review, not automatically checked.
Will the check change anything?
No. It reads public settings and makes a limited number of requests: DNS lookups through public resolvers, a few TLS handshakes and at most 8 HTTP requests per host, paced and with short timeouts, from Ironfang Security's published scanner address. It does not change your website or attempt to exploit it.
Why is there no score?
Ironfang reports findings rather than a grade. Each has a severity, for its potential impact, and a confidence, for how strong the evidence is. Fix the high-severity, high-confidence ones first.
Can I check individual settings?
Yes. Use the SSL/TLS, DMARC, security headers and DNS security checkers for a more focused result.