SPF Record Generator
Apne senders ko authorize karne wala SPF TXT record banaiye, ya existing record paste karke syntax check aur DNS lookup ko 10 ki limit se milaiye.
SPF Record Generator poori tarah aapke browser mein chalta hai. Records aapke device par banate-check hote hain — koi DNS query aur koi upload nahin.
DMARC Record Generator kholein
SPF Record Generator ke baare mein
SPF Record Generator wo ek TXT record banata hai jo receiving mail servers ko batata hai ki aapke domain ki taraf se kaun mail bhej sakta hai. Jin providers se aap bhejte hain unhe check karein — Google Workspace, Microsoft 365, SendGrid — wo unke documented include mechanisms mein badal jaate hain; apne server IP se add karein aur baaki sab ke liye policy chunein: ~all softfail jab tak aap senders discover kar rahe ho, -all rejection jab list complete ho jaaye. Checker koi bhi existing record waise hi analyze karta hai jaise receiver karta: v=spf1 prefix verify karta hai, deprecated ptr aur catastrophic +all flag karta hai, all ke baad ke bekaar terms ke liye warn karta hai jo receivers ignore karte hain, aur DNS-lookup mechanisms ko us hard limit 10 se count karta hai jo chupke se itne records tod deti hai.
Features
- Bade providers ke liye one-click includes
- ip4 aur ip6 mechanisms with address aur CIDR validation
- Apne hosts se bhejne wale domains ke liye a aur mx switches
- Chaaron all policies honestly explained
- RFC 7208 ki 10 limit ke against DNS lookup counter
- Sab kuch browser mein validate hota hai — koi remote query nahin
SPF Record Generator kaise use karein
- Un providers ko check karein jo aapke domain se mail bhejte hain
- Agar apne IPs hain toh add karein aur all policy set karein
- Record ko root domain ke TXT record mein daalein
- Ya check mode mein switch karke existing record paste karein
Example
Input
Google Workspace + SendGrid · ~all
Output
v=spf1 include:_spf.google.com include:sendgrid.net ~all
Allowed das mein se do DNS lookups — kaafi margin.
Common errors aur troubleshooting
- Record theek dikhta hai phir bhi mail SPF fail hoti hai. — Lookups gino: include, a, mx, ptr, exists aur redirect har ek ek lete hain, aur nested includes bhi count hote hain. Das ke paar receivers permerror lautate hain. Kam use hone waale includes ko ip4 mechanisms mein flatten karein.
- Domain par do SPF records hain. — Ye automatically permanent error hai. Sab mechanisms ko ek hi v=spf1 string mein merge karein: har domain par sirf ek SPF record allowed hai.
- Sab pass ho jaata hai — fake mail bhi. — +all dhoondhein, jo poore internet ko authorize karta hai aur record na hone se bhi bura hai. -all use karein, ya rollout ke dauraan ~all, aur DMARC ke saath pair karein.
Aksar pooche jaane wale sawaal
- SPF record kya hai aur mere domain ko kyun chahiye?
- Ye ek DNS TXT record hai jo un servers ki list deta hai jo aapke domain se mail bhej sakte hain. Receivers connecting server ko isse match karte hain; SPF ke bina koi bhi aapka address forge kar sakta hai.
- ~all par khatam karein ya -all par?
- ~all se shuru karein: failures mark hoti hain par deliver hoti hain, isliye bhoola hua sender mail nahin khota. Reports jab dikhayein ki har legitimate source pass ho raha hai, tab -all par jaayein.
- SPF ki 10 DNS lookup limit kya hai?
- RFC 7208 har evaluation mein DNS-querying mechanisms ko das tak limit karta hai, nested includes ke through recursively count hote hue. Cross karne par permerror milta hai, jise kaafi receivers failure jaisa treat karte hain. Har provider include usually ek se teen lookups leta hai.
- Kya akela SPF email spoofing rok deta hai?
- Nahin. SPF envelope sender check karta hai, visible From header nahin, aur plain forwarding par toot jaata hai. DKIM signatures aur DMARC policy ke saath combine karein — teeno mil kar hi asli authentication banate hain.
Related tools
Saare ArrayKit tools