adp.fr

Checked 22 October 2026, 01:25 UTC · via 8.8.8.8
!Passed with warnings
25 passed 5 warnings 0 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:23.90.116.100 ip4:23.90.122.11 ip4:185.14.244.9 ip4:185.14.245.9 ip4:185.14.246.9 ip4:185.14.247.9 ip4:141.95.202.172 include:_spf.profils.org mx -all
DNS lookups
2 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 2 of 10 DNS lookups #2
    SPF record needs 2 DNS lookups (limit is 10).
  • ✓ Ends with -all #3
    SPF record properly uses -all to restrict unauthorized senders.
  • ✓ Record published #6
    SPF record exists for this domain.
  • ✓ Single record #16
    Exactly one SPF record is published.
  • ✓ Valid syntax #25
    All SPF mechanisms and modifiers are valid.
  • ✓ No void lookups #26
    All include/redirect targets exist.
  • ✓ No overly broad IP ranges #27
    All ip4/ip6 ranges are narrow enough.

DMARC

pass

p=reject (_dmarc.adp.fr)

Found

Record
v=DMARC1;p=reject;sp=reject;np=reject;rua=mailto:e1lbuyti@ag.eu.dmarcadvisor.com;ruf=mailto:dmarc_ruf@adp.fr;fo=1
Found at
_dmarc.adp.fr
External report address
mailto:e1lbuyti@ag.eu.dmarcadvisor.com (authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
sprejectSubdomain policy
ruamailto:e1lbuyti@ag.eu.dmarcadvisor.comAggregate report addresses
rufmailto:dmarc_ruf@adp.frFailure report addresses
fo1Failure reporting options
npreject

Checks

  • ✓ Policy: reject #4
    DMARC policy is set to 'reject', which provides the strongest protection against email spoofing.
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Applies to 100% of mail #18
    DMARC policy applies to all failing mail.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:e1lbuyti@ag.eu.dmarcadvisor.com
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: k1, mx, s1, s2

Found

Selectors
k1, mx, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
k1RSA 1024 bits
mxRSA 1024 bits
s1RSA 2048 bits
s2RSA 1024 bits

Checks

  • ✓ Keys found: k1, mx, s1, s2 #7
    DKIM keys found for this domain with selectors: k1, mx, s1, s2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: k1 (1024 bits), mx (1024 bits), s2 (1024 bits). Rotate to a 2048-bit key.
    #23
  • ✓ No problematic flags #24
    No keys in test mode, revoked, or limited to SHA-1.

DNSSEC

warn

Signed, but no DS at parent

Found

DNSKEY records
Yes (2)
DS at parent
No
Algorithms
RSASHA256 (8)
Key tags
54234, 58411
Signatures valid until
24 October 2026, 01:04 UTC

Checks

  • !
    Signed, but no DS at parent
    The zone is signed (DNSKEY present) but the parent has no DS record, so the chain of trust is incomplete. Publish the DS record at your registrar.
    #8
  • !
    Signatures expire in 48h0m0s
    DNSKEY signatures expire at 2026-10-24T01:04:02Z (in 48h0m0s). Check that re-signing works.
    #21

MX

warn

2 mail servers

Found

PriorityHostRecordsReverse DNS
20mx1.hc1073-58.eu.iphmx.comA 23.90.117.254 A 23.90.116.98esa.hc1073-58.eu.iphmx.com ✓ esa.hc1073-58.eu.iphmx.com ✓
20mx2.hc1073-58.eu.iphmx.comA 23.90.116.98 A 23.90.117.254esa.hc1073-58.eu.iphmx.com ✓ esa.hc1073-58.eu.iphmx.com ✓

Checks

  • ✓ 2 MX records #9
    Found 2 MX records for this domain.
  • ✓ All hosts resolve #10
    All MX records resolve to valid IP addresses.
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: mx1.hc1073-58.eu.iphmx.com, mx2.hc1073-58.eu.iphmx.com
    #11
  • ✓ Redundant MX hosts #12
    Found 2 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 2 MX records, which is within the recommended range (1-5).
  • ✓ No localhost targets #14
    No MX records pointing to localhost found.
  • ✓ No private IP addresses #15
    No MX records resolving to private IP addresses found.
  • ✓ No CNAME targets #22
    No MX records point to a CNAME.
  • ✓ Reverse DNS confirmed #30
    All 4 MX addresss have a PTR record that resolves back to them.

TLS

warn

no MTA-STS · no TLS-RPT · DANE on 0 of 2 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx1.hc1073-58.eu.iphmx.comnone-
mx2.hc1073-58.eu.iphmx.comnone-

Checks

  • !
    Not configured
    MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.
    #32
  • i
    Not configured
    TLS-RPT lets senders report TLS delivery problems to you. It is most useful together with MTA-STS or DANE.
    #35
  • i
    Not used
    No MX host publishes TLSA records. DANE lets senders verify your mail server's certificate through DNSSEC; it requires DNSSEC on the MX host's zone.
    #36

BIMI

info

No BIMI record

Checks

  • i
    Not configured
    BIMI shows your logo next to your mail in supporting mail clients. It requires DMARC enforcement.
    #38