Skip to main content

Security Badge

Generate a live security posture badge for any scanned domain. Embed it in your GitHub README, documentation, blog, or website.

Live Preview
detailed
Generate Badge
Enter a domain name or a scan number from any report URL.
Style
Where to Find Your Scan Number

After running a scan, look at the URL in your browser address bar:

dnstool.it-help.tech/analyze?domain=example.com&id=1234

The number after id= is your scan number. Using a scan number pins the badge to that specific scan result.

Using a domain name always shows the most recent public scan.

Embed Code
Animated Badge

Full-color animated PNG. Crystal clear, lossless quality. Supported by all modern browsers, Apple Mail, Notion, and most platforms.

256-color animated GIF. Universal compatibility for legacy platforms. Use APNG for full quality.

Animated DNS Topology Badge

This badge visualizes publicly available DNS records, certificate transparency logs, and protocol configurations — the same data queryable via dig, nslookup, or any CT log search. Domains missing SPF, DKIM, DMARC, or DNSSEC records are verifiably exposed to spoofing, impersonation, and interception. That is not an opinion. It is what the protocol specifications require and what the absence of those records permits.

GitHub & Shields.io

Use the Shields.io endpoint for dynamic badges rendered by Shields.io. These always produce their standard compact format.

Private scans are excluded. Only public domain posture data is exposed. Badge data cached for 1 hour.

Where Each Badge Works
Detailed — Topology-style assessment card with score gauge, protocol nodes (SPF, DKIM, DMARC, DNSSEC, DANE, MTA-STS, TLS-RPT, BIMI, CAA), risk level, and scan date. Works in GitHub README (![](url)), any website, documentation, wikis. Our server renders the SVG — full control over the design.
Compact — Shields-style inline badge showing your domain and risk level. Works everywhere including Shields.io integration. For CI dashboards, inline references, and anywhere you need a quick visual indicator.
Covert — Terminal-aesthetic card. For security researchers, red-team documentation, and anyone who likes their indicators dark.
GitHub compatibility: All three styles work in GitHub README files. Use the Direct Image URL in Markdown. Shields.io always renders its own compact format regardless of which style you select here.
Straight talk about your data.

We use two cookies, both essential:

  • _csrf — Prevents cross-site request forgery. Required for form submissions. Security-only.
  • _dns_session — Only exists if you choose to sign in. No account required to use DNS Tool.

We log your IP address for two reasons: rate limiting (so nobody abuses the service) and security (identifying malicious actors and complying with legal obligations). We check source geography for analysis accuracy — DNS responses vary by region, and knowing which resolver answered from where makes the science better.

No tracking cookies. No analytics cookies. No ad networks. No data brokers. Our code is open-core — the application framework is publicly available under BUSL-1.1 with timed Apache-2.0 conversion. Verify it yourself.

If you create an account and want out, account deletion removes your login and scan history. Public domain analyses remain available because they contain only public DNS records, already hashed. Full details: Privacy Policy.