Medido el 2026-07-12 · DNS público
¿Está ch-perpignan.fr protegido contra la suplantación de correo?
Todavía no — ch-perpignan.fr solo observa (p=none); el correo suplantado aún puede entregarse.
Postura sin cambios desde el 2026-06-19
Más protegido que el 26 % de grandes hospitales en Francia
El 10 % del sector ya aplica p=reject
D
DMARC
p=none
SPF
-all
DKIM
1 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;Qué significa esto
- • Politique p=none : surveillance seule, aucun message non authentifié n'est bloqué.
- • Aucune adresse rua : tu ne reçois pas les rapports agrégés, impossible de piloter le durcissement.
- • Au moins une clé DKIM valide publiée.
Historial
- 2026-06-26Primera mediciónSolo observación (p=none)
Sobre CH de Perpignan
The Centre Hospitalier de Perpignan is a major public health facility located in Occitania, France. This university hospital serves thousands of patients annually through its general medicine, specialized care, and emergency services. Its IT infrastructure manages a substantial volume of official communications, ranging from internal clinical exchanges to correspondence with patients, private practitioners, health insurance organizations, and regulatory authorities.
Securing the ch-perpignan.fr domain holds critical strategic importance for the Centre Hospitalier. Healthcare institutions are prime targets for phishing attacks and domain spoofing, particularly due to the sensitivity of data processed and the trust placed in official communications. A compromise of email authentication could facilitate identity fraud, malware distribution, or unauthorized access to protected health information.
Within a context of strengthened French and European regulatory frameworks, implementing a robust DMARC strategy aligns with IT governance and cybersecurity requirements. The ch-perpignan.fr domain requires an optimized DMARC configuration, coupled with SPF and DKIM, to ensure message authenticity and prevent abuse. This approach protects both the institution against reputational harm and end users against fraud schemes.