culture.fr

Checked 22 October 2026, 02:29 UTC · via 8.8.8.8
✗Problems found
19 passed 4 warnings 2 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:143.126.211.0/24 ip4:92.103.206.104 include:message-business.com include:spf.protection.outlook.com -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

fail

p=none (_dmarc.culture.fr)

Found

Record
v=DMARC1;p=none;pct=100;adkim=r;aspf=r;sp=none; fo=1
Found at
_dmarc.culture.fr
TagValueMeaning
vDMARC1Version
pnonePolicy
spnoneSubdomain policy
pct100Percentage of mail the policy applies to
adkimrDKIM alignment (r = relaxed, s = strict)
aspfrSPF alignment (r = relaxed, s = strict)
fo1Failure reporting options

Checks

  • ✗
    Policy: none (monitoring only)
    DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • !
    No aggregate reports (rua)
    DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19

DKIM

fail

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NXDOMAIN

Checks

  • ✗
    No DKIM keys published
    _domainkey.culture.fr does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7

DNSSEC

warn

Signed, but no DS at parent

Found

DNSKEY records
Yes (12)
DS at parent
No
Algorithms
ECDSAP256SHA256 (13)
Key tags
829, 27865, 48264, 63747, 58609, 44277, 16029, 50550, 14982, 57469, 10427, 7839
Signatures valid until
20 November 2026, 12:29 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 valid until 2026-11-20 #21
    DNSKEY signatures are valid until 2026-11-20T12:29:10Z.

MX

warn

4 mail servers

Found

PriorityHostRecordsReverse DNS
10mx01.m18.pfai.din.gouv.frA 143.126.248.50mx01.m18.pfai.din.gouv.fr ✓
10mx02.m18.pfai.din.gouv.frA 143.126.249.50mx02.m18.pfai.din.gouv.fr ✓
10mx03.m18.pfai.din.gouv.frA 143.126.250.50mx03.m18.pfai.din.gouv.fr ✓
10mx04.m18.pfai.din.gouv.frA 143.126.251.50mx04.m18.pfai.din.gouv.fr ✓

Checks

  • ✓ 4 MX records #9
    Found 4 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: mx01.m18.pfai.din.gouv.fr, mx02.m18.pfai.din.gouv.fr, mx03.m18.pfai.din.gouv.fr, mx04.m18.pfai.din.gouv.fr
    #11
  • ✓ Redundant MX hosts #12
    Found 4 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 4 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 4 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx01.m18.pfai.din.gouv.frnone-
mx02.m18.pfai.din.gouv.frnone-
mx03.m18.pfai.din.gouv.frnone-
mx04.m18.pfai.din.gouv.frnone-

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