Recursos · 34

Mejorar la confianza y la capacidad de entrega del remitente del correo electrónico

Verificar identidad del remitente, clases de mensajes, comportamiento de baja y causas de rechazo.

Actualizado · 8 min

Bastidores de comunicaciones y cableado de red en una sala vacía Ilustración editorial generada con IA

Lo que esta guía ayuda a lograr

  • Flujos de mapa
  • Autenticar dominios
  • Habilitar retiro
  • Diagnosticar rechazos

Comprobación rápida

  • ¿Qué sistemas envían bajo el dominio?
  • ¿Los mensajes reales pasan las comprobaciones SPF, DKIM y DMARC esperadas?
  • ¿Cada mensaje es promocional o transaccional?
  • ¿Funciona la baja requerida?
  • ¿Los rechazos se agrupan por causa?

Método paso a paso

  1. 1

    Envío de inventario

    Separar newsletters, automatizaciones, recibos y alertas. Registre dominio, proveedor, volumen, propósito y propietario de cada flujo.

    Entregable: mapa de flujo y dominio.

  2. 2

    Comprobar autenticación

    Pruebe SPF, DKIM, DMARC y alineación desde el dominio en muestras entregadas. Una configuración DNS esperada no demuestra que todas las rutas de envío funcionen.

    Entregable: encabezados inspeccionados y resultados de autenticación.

  3. 3

    Cumplir con las expectativas del destinatario

    Consulta el alta, la frecuencia, el contenido prometido y la separación del tráfico promocional y transaccional. Evite promociones inesperadas en los mensajes de servicio.

    Entregable: reglas por clase de mensaje.

  4. 4

    Baja de prueba

    Para el correo promocional aplicable, verifique un enlace visible y un comportamiento de un clic que coincida con los requisitos del proveedor y RFC 8058. Pruebe que la eliminación realmente se procese.

    Entregable: evidencia de baja de extremo a extremo.

  5. 5

    Ver reputación

    Seguimiento de rechazos permanentes y temporales, quejas y señales destinatario-proveedor. Analice por flujo y proveedor en lugar de un promedio global.

    Entregable: análisis de causa de no entrega.

  6. 6

    Arreglar y volver a probar

    Autenticación de direcciones, listas no calificadas, errores técnicos y bajas rotas de suscripción primero. Suba el volumen gradualmente cuando el contexto lo requiera.

    Entregable: plan de corrección y resultado observado.

Indicadores de gestión

IndicadorQué midePrimera acción
AutenticaciónMensajes reales con resultados SPF/DKIM/DMARC esperadosArreglar ruta de envío
RechazosTasa y causas por caudalLista limpia o reparación
RetiroSolicitudes promocionales aplicadasArreglar encabezados y procesamiento
QuejasInformes rastreados por campañaRevisar segmentación y frecuencia

Errores comunes

  • Asumiendo que el DNS publicado prueba cada flujo
  • Mezclando correo transaccional y promocional
  • Confundir una apertura con la ubicación de la bandeja de entrada
  • Mostrando un enlace para darse de baja que en realidad no elimina a un destinatario

Preguntas frecuentes

¿Es suficiente el SPF por sí solo?

No. Los requisitos de los destinatarios varían según el volumen y el contexto; Verifique DKIM, DMARC y la alineación aplicable también.

¿Cada mensaje necesita un clic?

Las reglas del proveedor distinguen mensajes promocionales y transaccionales, por lo que clasifica cada flujo primero.

¿Un abierto prueba la entrega?

No. Las métricas abiertas tienen sus propios límites y no reemplazan los resultados de entrega.

Seguridad del correo: identidad, alineación y transporte

Las notas detalladas de esta edición están disponibles en inglés.

Domain authentication, transport confidentiality and inbox placement are different questions. SPF, DKIM and DMARC inform domain identity; MTA-STS and DANE concern server-to-server connections; reports help observe failures. None of these signals proves a message is benign.

References and status checked on .

Which mechanism answers which question?

Which mechanism answers which question?
Mechanism and sourceWhat is checkedWhere to find evidenceLimit to retain
SPF

SPF · RFC 7208

Authorisation of the sending IP for the SMTP envelope domain; DMARC uses MAIL FROM.The evaluated domain’s TXT record and receiver result. Evaluation allows 10 DNS-querying terms, rather than simply 10 network requests.Forwarding may change the observed IP. Selecting multiple SPF records produces permerror; an SPF pass does not prove alignment with From.
DKIM

DKIM · RFC 6376

DKIM cryptography · RFC 8301

Cryptographic verification of signed message parts for the signature’s d= domain.DKIM-Signature, selector s=, domain d= and key under selector._domainkey. RFC 8301 requires RSA ≥ 1,024 bits, recommends ≥ 2,048 bits and excludes rsa-sha1.A valid signature from another domain may not satisfy DMARC. Changes to signed parts can break verification; DKIM does not encrypt the message.
DMARC

DMARC · RFC 9989

Links the visible From domain to at least one SPF- or DKIM-authenticated, aligned identifier.The TXT policy discovered through _dmarc and trustworthy results produced at reception. Record alignment mode and the domain actually evaluated.A pass neither guarantees delivery nor endorses content. Receivers retain local policy; DNS errors and non-conforming messages require separate handling.
DMARC aggregate / failure reports

DMARC aggregate reports · RFC 9990

DMARC failure reports · RFC 9991

Observation of streams using the domain: aggregate statistics and, separately, details about failing messages.rua / ruf destinations, covered period and received reports. Their formats are now specified in separate RFCs published in May 2026.Missing reports do not prove no mail was sent. Detailed reports may expose message data; define suitable access, minimisation and retention.
MTA-STS

MTA-STS · RFC 8461

Recipient-domain policy for SMTP TLS transport and expected MX hosts._mta-sts TXT, HTTPS policy at /.well-known/mta-sts.txt and certificate. Three modes: testing, enforce and none.Applies to supporting servers and transport, without end-to-end encryption. Initial discovery and caching have their own limits.
TLS-RPT

SMTP TLS Reporting · RFC 8460

Reporting of successful and failed TLS negotiation or validation between servers._smtp._tls TXT, reporting destinations and received JSON data, correlated with transport logs.Observation does not enforce encryption. TLS reports and DMARC domain-identity reports describe different events.
DANE for SMTP

DANE for SMTP · RFC 7672

TLS transport authentication using DNSSEC-protected TLSA records.Validated DNSSEC chain, SMTP service TLSA record and a match with the presented certificate or key.DNSSEC validation is required on this path. DANE does not validate From or replace SPF, DKIM and DMARC.
ARC

ARC · RFC 8617

Carries authentication assessments along paths involving intermediaries.ARC header sets, chain validation and a trust decision about intermediaries.RFC 8617 is Experimental. ARC is not a trust framework and does not automatically make a message safe or deliverable.

DMARC in 2026: documentation changes

Reference
RFC 9989, published in May 2026, replaces RFC 7489 and RFC 9091. Aggregate and failure reporting are separated into RFC 9990 and RFC 9991.
Discovery and alignment
The specification defines DNS Tree Walk discovery. Do not infer organisational domains by naively retaining the final two labels.
Testing a deployment
pct is removed; the new t=y requests handling one level below the published failure policy: reject becomes quarantine, and quarantine becomes none. t=n is the default.
Interoperability
The standard advises against p=reject for general-purpose email domains. Inventory forwarding and mailing lists and check actual implementations before changing policy.

Publication of an RFC does not show that every provider already implements that version. Check documentation, observed results and exceptions in your own streams. These examples are educational and provide no ready-to-deploy DNS record. RFC 9989 →

Understand DMARC logic with a scenario

Simplified model: a conforming From message, an already discovered DMARC policy, one SPF MAIL FROM result and one examined DKIM signature. You supply alignment based on the evaluated domains and mode. The tool performs no DNS resolution or signature verification and predicts no delivery.

(SPF pass AND aligned) OR (DKIM pass AND aligned)

With multiple DKIM signatures, check each result / d= pair: one valid, aligned signature can suffice. Never combine one signature’s pass with an aligned domain from another failing signature. DNS discovery errors, absent policy and invalid From fields are outside this model. All choices stay in your browser.

Six educational cases, readable without JavaScript

Six educational cases, readable without JavaScript
ScenarioSPF: result / alignmentDKIM: result / alignmentExpected interpretation
Aligned SPF is sufficientpass — authenticated
Yes
fail — observed failure
No
pass — at least one authenticated and aligned path

The SPF path meets both conditions.

Aligned DKIM is sufficientfail — observed failure
No
pass — authenticated
Yes
pass — at least one authenticated and aligned path

The DKIM path meets both conditions independently of the other path in this model.

Two passes without alignmentpass — authenticated
No
pass — authenticated
No
fail — no authenticated and aligned path in this scenario

Two third-party domains passing technically does not validate From.

Aligned domains, no authenticationfail — observed failure
Yes
fail — observed failure
Yes
fail — no authenticated and aligned path in this scenario

A matching domain does not replace successful authentication.

Incomplete evidenceResult not supplied
Alignment not supplied
fail — observed failure
No
Undetermined — complete the observations

Missing evidence on one path cannot be invented.

Proven DKIM, unknown SPFResult not supplied
Alignment not supplied
pass — authenticated
Yes
pass — at least one authenticated and aligned path

One complete positive result suffices even when the other path is unknown.

Prepare an actionable email review

Prepare an actionable email review
StreamEvidence to correlateUseful decision
Alerts, receipts and resetsProvider and From domain, envelope and DKIM identities, tracking ID, SMTP response and available delivery event.Separate transport failure, authentication error and absence of reading. Define an alternative for a critical service.
Campaigns and newslettersDomains and subdomains, alignment results, representative samples from every platform, withdrawal mechanism and stream-specific errors.Repair the affected sending path before changing a global policy; do not equate authentication with recipient expectations.
Forwarding and mailing listsPath before and after the intermediary, message changes, SPF/DKIM outcomes and ARC information when present.Explain the observed break and local policy; do not assume a valid ARC chain compels acceptance.
Transport to MX hostsRelevant MTA-STS policy or TLSA, certificates, DNSSEC validation for DANE, TLS reports and timestamped logs.Associate failures with the relevant host and period. Test changes within authorised scope and retain rollback.

Continue with domain and DNS governance →

Primary sources and publication dates

Dates below identify RFC publication months, separately from the consultation date. Descriptions and cases are editorial summaries rather than complete normative extracts.

Referencias oficiales

Las referencias respaldan el método. Adapte los controles a su contexto; no constituyen certificación. Los títulos de referencia originales y los documentos fuente pueden estar en otro idioma.