CONSOLE
Loading
Scan your sending domain in 5 seconds. Identify SPF 10-lookup limits, missing DMARC policies, weak DKIM keys, and MX routing flaws before your emails hit the spam folder.
Understanding the strict enforcement rules that dictate whether your transactional alerts land in the primary inbox or the spam folder.
| Requirement | Why ISPs Enforce It | How PhotonRelay Handles It |
|---|---|---|
| Mandatory SPF & DKIM | Confirms that the sending server has explicit authorization to dispatch mail on behalf of the domain, eliminating spoofed sender addresses. | Automated Built-in SPF routing and automatic 2048-bit cryptographic DKIM key rotation on all outgoing messages. |
| DMARC Alignment | Instructs receiving mail servers what action to take when emails fail SPF or DKIM checks, preventing brand impersonation. | Included Guided DMARC progression from p=none monitoring to strict p=reject enforcement. |
| Spam Rate Below 0.3% | Google Postmaster Tools strictly flags domains whose user-reported spam complaints exceed 0.10% (target) and 0.30% (blocking threshold). | Reputation Shield Automated real-time bounce suppression and isolated IP routing protect your sending reputation. |
| Valid Forward & Reverse DNS (PTR) | Receiving mail servers cross-check that sending IP addresses resolve back to the sender's verified hostname. | Pre-Configured 100% of PhotonRelay Anycast edge nodes maintain synchronized rDNS PTR records. |
Even with clean code, subtle DNS errors can silently destroy your domain reputation.
RFC 7208 limits DNS lookups to exactly 10. If third-party SaaS tools push your lookup depth to 11, mail servers return a PermError and reject messages automatically.
Legacy 1024-bit RSA keys can be brute-forced with modern cloud computing. Major mailbox providers now favor or require 2048-bit keys for maximum trust.
Publishing two separate TXT records starting with v=spf1 completely breaks authentication. RFC mandates that all includes must be combined into one single record.
Leaving DMARC at p=none forever provides zero defense against bad actors spoofing your domain. Spammers can freely impersonate your brand without triggering spam filters.
include:, a, mx, and redirect) to prevent denial-of-service loops. If your domain exceeds 10 lookups, receiving mail servers trigger a PermError and reject messages. To fix this, you must "flatten" your SPF record or remove unused vendor includes.
p=none and monitor aggregate feedback reports via the rua= tag for 2 to 4 weeks to identify all legitimate sending services. Once verified, graduate to p=quarantine; pct=25; and incrementally scale up to pct=100 before finally enforcing p=reject.