Medido el 2026-07-11 · DNS público
¿Está atombank.co.uk protegido contra la suplantación de correo?
Todavía no — atombank.co.uk solo observa (p=none); el correo suplantado aún puede entregarse.
Postura sin cambios desde el 2026-06-19
Más protegido que el 4 % de bancos en Reino Unido
El 70 % del sector ya aplica p=reject
D
DMARC
p=none
SPF
~all
DKIM
3 selector(es)
Cómo corregirlo
Thomas, tu CISO virtual con IA, identifica cada fuente, escribe el DNS exacto y lleva tu dominio de p=none a p=reject con total seguridad.
Registro publicado
v=DMARC1; p=none; rua=mailto:atombank@rua.netcraft.com; ruf=mailto:atombank@ruf.netcraft.com;Qué significa esto
- • Politique p=none : surveillance seule, aucun message non authentifié n'est bloqué.
- • SPF se termine par ~all (softfail) : acceptable en phase d’observation, viser -all à terme.
- • Au moins une clé DKIM valide publiée.
Historial
- 2026-07-04DKIMSolo observación (p=none)
- 2026-06-26Primera mediciónSolo observación (p=none)
Sobre Atom Bank
Atom Bank is a French financial institution operating under the domain atombank.co.uk, representing a significant player in the European digital banking sector. As a financial services organization, Atom Bank manages a complex email ecosystem encompassing internal communications with employees, customer correspondence, critical transactional notifications and exchanges with institutional partners. The atombank.co.uk domain serves as an essential communication vector for authenticating official messages and maintaining customer trust. Email security challenges for a bank are substantial: domain spoofing could facilitate phishing attempts targeting customers, compromise sensitive data and damage institutional reputation. Within the European regulatory context, Atom Bank is subject to strengthened cybersecurity obligations, particularly through the NIS2 Directive and potentially the DORA Regulation which apply to critical financial sector entities. Robust DMARC implementation on atombank.co.uk becomes a strategic necessity to authenticate legitimate messages, prevent identity spoofing fraud and demonstrate compliance with email security standards. A well-configured DMARC policy ensures that only authorized mail servers can send messages on behalf of the domain, protecting customers against targeted phishing attacks and strengthening the organization's overall security posture.