📧
Email DNS Generator
Build custom SPF, DKIM & DMARC records
Configuration
Authorized Senders
Allow MX servers Servers listed in domain's MX records can send mail
Allow A record IP The domain's primary A/AAAA record IP can send mail
Allow IPv6 (AAAA) Add ip6: mechanism for IPv6 address of A record
Third-Party Includes
Common Providers
Additional IP Addresses
Enforcement Policy (all)
ℹ ~all (SoftFail): Unauthorized mail is tagged but delivered. Recommended while testing.
Generated SPF Record
DNS Record Type TYPE
TXT
Host / Name HOST
@
TXT Value RECORD
v=spf1
TTL TTL
3600 (1 hour — standard for SPF)
SPF Mechanism Reference
v=spf1Required version tag — must always be first
mxAuthorizes the MX servers defined for this domain
aAuthorizes the IP of the domain's A/AAAA record
include:Delegates authorization to another domain's SPF record (counts toward lookup limit)
ip4:Authorizes a specific IPv4 address or CIDR range (e.g., ip4:203.0.113.0/24)
ip6:Authorizes a specific IPv6 address or prefix
-allHard fail — reject unlisted senders (recommended for production)
~allSoft fail — tag unlisted senders (recommended while testing)
?allNeutral — take no action on unlisted senders
Configuration
Restrict to exact domain only Adds s=email — prevents use on subdomains
Testing mode Adds t=y — signals receivers key is in testing
Generated DKIM Record
DNS Record Type TYPE
TXT
Host / Name HOST
Enter domain & selector above
TXT Value RECORD
Complete the form above
TTL TTL
3600 (1 hour — standard for DKIM)
DKIM Tag Reference
v=DKIM1Required version tag — must always be first
k=rsaKey type — rsa (default) or ed25519
p=<key>The Base64-encoded public key. If empty (p=), key is revoked
s=emailService type restriction. Omit to allow all mail services
t=yTesting flag — receivers should treat failures leniently
t=sSubdomain restriction — key cannot be used by subdomains
h=sha256Acceptable hash algorithms (sha256 or sha1)
ℹ Key source: Your DKIM public key is generated by your mail provider (Google Workspace, Microsoft 365, SendGrid, etc.). Retrieve it from your provider's DNS settings panel, then paste only the Base64-encoded key block here — without -----BEGIN PUBLIC KEY----- headers.
Domain & Policy
100%
Strict DKIM alignment (adkim=s) Default: relaxed (r) — allows subdomains
Strict SPF alignment (aspf=s) Default: relaxed (r) — allows subdomains
Reporting Configuration
Generated DMARC Record
DNS Record Type TYPE
TXT
Host / Name HOST
Enter domain above
TXT Value RECORD
Complete the form above
TTL TTL
3600 (1 hour — standard)
DMARC Tag Reference
v=DMARC1Required version tag — must always be first
p=Policy: none (monitor), quarantine (spam), reject (block)
sp=Subdomain policy override — defaults to p= if omitted
pct=Percentage of mail to apply policy to (0–100). Start at 10% when deploying
rua=URI for aggregate XML reports (mailto: or https:). Highly recommended
ruf=URI for forensic/failure reports. Contains sample message data — use carefully
adkim=DKIM alignment: r=relaxed (default), s=strict (exact domain match)
aspf=SPF alignment: r=relaxed (default), s=strict (exact domain match)
fo=Forensic reporting trigger: 0=all fail (default), 1=any fail, d=DKIM, s=SPF
ri=Report interval in seconds. Default: 86400 (24 hours)
⚠ Deployment tip: Always start with p=none; pct=10 and a rua= address. Monitor aggregate reports for 2–4 weeks before progressing to quarantine or reject. Jumping to reject immediately can silently drop legitimate email.
Share MySysAd

⚠️ IMPORTANT DISCLAIMER: The tools and scripts on this site are provided "AS IS" for educational purposes.

Review destructive commands before executing. By using this site, you assume all risk and agree to our Full Terms of Service.