Inspección técnica de políticas _dmarc: evaluación de modos p=none, p=quarantine y p=reject, alineación criptográfica y buzones de reporte agregado RUA.
Stateless edge execution • Zero database retention • No user tracking or behavioral profiling
Every network lookup executes inside a temporary, isolated V8 sandbox deployed across Cloudflare's global edge. Each isolate is instantiated on demand, parses public DNS or TLS socket records in transient RAM, returns the result stream, and terminates immediately.
IncogSay operates under a strict zero-retention guarantee. Target domains, submitted URLs, and user IP addresses are never written to disk, stored in relational databases, or logged in persistent files. We do not maintain historical query logs or link lookups to user identities.
All tools are completely free and functional without registration, user logins, or account creation. We never deploy invasive session fingerprints, third-party analytics trackers that capture input payloads, or behavioral profilers. Your queries remain ephemeral and anonymous.
Ingresa tu dominio principal en el verificador.
Pulsa "COMPROBAR DMARC" para interrogar al subdominio _dmarc.
Revisa el estado de la directiva de aplicación p (none, quarantine o reject).
Confirma la configuración de los destinos de reporte rua para monitorizar intentos de suplantación.
Publicar una política DMARC estricta con p=reject es el único mecanismo estandarizado para impedir que atacantes emitan correos fraudulentos simulando ser tu empresa. Además, es un requisito previo indispensable para la implementación de certificados VMC y logotipos BIMI en bandejas de entrada compatibles.
Enterprise email delivery relies on a four-tier cryptographic and policy stack. This tool executes statelessly against public authoritative nameservers to audit each protocol layer in real time.
Validates the Return-Path against designated sending MTA IP ranges. Strictly calculates recursive lookup depth against the 10-DNS-query boundary to prevent delivery-breaking permerror statuses.
Retrieves public RSA (2048-bit minimum) or Ed25519 public keys at selector DNS records, ensuring cryptographic non-repudiation and transit tamper detection for canonicalized body hashes.
Enforces strict alignment between the visible From domain and SPF/DKIM authenticated identifiers. Dictates receiver disposition across none, quarantine, and reject policies.
Enforces TLS in transit via MTA-STS policy files and renders verified trademarked SVG Tiny PS brand logos under VMC certificates in Gmail, Yahoo, and Apple Mail inboxes.
Common administrative and operational scenarios solved by this tool
Audit sending domains against Google and Yahoo's mandatory bulk sender requirements. Confirm that your domain publishes valid SPF and DKIM records, maintains strict DMARC alignment, and prevents rejection when delivering to over 5,000 daily consumer recipients.
Identify when combining multiple SaaS providers (Google Workspace, Zendesk, Mailchimp, Salesforce) causes your SPF record to exceed RFC 7208's strict 10-lookup threshold, triggering permanent authentication failures at receiving mail gateways.
Verify whether your domain allows bad actors to forge your sender address in phishing campaigns. Test whether your DMARC policy enforces quarantine or reject, stopping business email compromise (BEC) and unauthorized outbound spoofing.
Confirm that automated marketing platforms and transactional gateways (SendGrid, Postmark, Amazon SES) have published valid 2048-bit DKIM keys at their assigned selector records before initiating outbound marketing or password-reset campaigns.
Direct, peer-reviewed engineering answers to core deployment, troubleshooting, and compliance questions.
DMARC vincula los resultados de SPF y DKIM y comunica a los servidores receptores exactamente qué hacer si un correo con tu nombre de dominio no supera la autenticación, evitando ataques de spoofing y phishing.
Comienza publicando p=none para recopilar reportes RUA durante varias semanas. Una vez que hayas identificado y autorizado todos tus proveedores legítimos (CRM, facturación, marketing), cambia a p=quarantine y finalmente a p=reject.