vulnbeacon_TOOLS
← All tools

DNS & email

Email security

Review DNS-based mail configuration. Record presence alone does not establish deliverability or prevent every form of spoofing.

How to use Email securitySteps, privacy & next steps

Inspect the MX, SPF and DMARC records published at your domain.

Run this check

  1. Enter a domain name rather than a mailbox or page URL.
  2. Confirm permission and consent to the disclosed Cloudflare DNS lookup.
  3. Review the published records with your mail administrator before changing sender policy.

What you need

  • The exact domain whose mail records you want to inspect.

Your input & privacy

The domain is sent to Cloudflare DNS over HTTPS after consent. No message or mailbox content is accessed.

Read the result

Use the record observations to review legitimate senders and policy rollout. Test authorized mail before enforcing stricter policy.

Keep in mind

  • No mail is sent. DKIM selectors, SPF include expansion and organizational-domain DMARC inheritance are not evaluated.
  • Record presence alone does not establish delivery, alignment or protection against every spoofing method.

Your inputs, explained.

JWTs, source snippets, passwords, CSP text, files, hashes and Base64 are processed in browser memory. This toolkit does not upload or save those inputs.

Website checks send the approved URL to this service and contact the target. DNS checks disclose the domain to Cloudflare DNS over HTTPS. Email-breach checks send the full address to Have I Been Pwned when configured and explicitly requested.

Server checks are transient and rate limited. This application does not write tool input or result logs; your hosting provider and contacted services may retain network metadata under their own policies. Exports are saved only when you choose to download them.

Use tools only for assets you own or have permission to assess. Private scans and their saved reports use the separate authenticated VulnBeacon application.