Answers to common questions about authentication, deliverability, and how we operate.
SPF authorizes which servers may send for your domain. DKIM cryptographically signs each message so receivers can verify integrity and origin. DMARC ties the two together, tells receivers how to handle failures, and provides reporting. All three should be configured for reliable delivery.
Technically you can send without one, but many major providers (Gmail, Outlook, Yahoo) reject or spam-filter mail from IPs lacking valid PTR. Best practice is forward-confirmed reverse DNS: the IP resolves to a hostname, and that hostname resolves back to the same IP.
SPF permits a maximum of 10 DNS lookups during evaluation. Each include: mechanism counts toward this limit (including nested ones), while ip4: and ip6: do not. Our SPF generator flags when you approach the limit.
No. SPF only governs outbound sending. Receiving mail is controlled by your MX records. You can change or tighten SPF without affecting inbound delivery.
Begin with p=none to monitor without affecting delivery, review aggregate reports for a few weeks, then move to p=quarantine and finally p=reject once all legitimate sources pass alignment.
We only send permission-based mail, enforce a strict Acceptable Usage Policy, include one-click unsubscribe on every message, classify bounces, suppress complaints, and respond to abuse reports within 24 hours.
Use the one-click link in any email, visit our unsubscribe page, or email unsubscribe@premiumservice.club. Removal is immediate and permanent.
Yes. The SPF and DMARC generators run entirely in your browser — nothing is sent to our servers. The DNS lookup uses public DNS-over-HTTPS to fetch records for the domain you enter.