pourquoidocteur.fr

Checked 22 October 2026, 04:52 UTC · via 8.8.8.8
✗Problems found
17 passed 6 warnings 2 failed 3 info

SPF

warn

SPF record published

Found

Record
v=spf1 a mx ptr ip4:94.23.96.1 ip4:94.23.96.3 ip4:94.23.96.4 ip4:94.23.96.5 ip4:94.23.96.6 ip4:94.23.96.7 ip4:94.23.96.8 ip4:94.23.96.9 ip4:94.23.96.10 ip4:94.23.96.11 ip4:176.31.223.17 ip4:176.31.223.19 ip4:176.31.223.20 ip4:176.31.223.21 ip4:176.31.223.25 ip4:94.23.35.126 ip4:94.23.27.214 ip4:5.135.61.66 ip4:176.31.223.22 ip4:176.31.223.24 ip4:176.31.223.26 ip4:5.135.61.66 ip4:137.135.168.155 ~all
DNS lookups
3 of 10
Void lookups
0 of 2

Checks

  • !
    Uses deprecated ptr mechanism
    The ptr mechanism in SPF records is deprecated due to performance issues and should be avoided.
    #1
  • ✓ 3 of 10 DNS lookups #2
    SPF record needs 3 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.pourquoidocteur.fr)

Found

Record
v=DMARC1; p=none; sp=none; aspf=r
Found at
_dmarc.pourquoidocteur.fr
TagValueMeaning
vDMARC1Version
pnonePolicy
spnoneSubdomain policy
aspfrSPF alignment (r = relaxed, s = strict)

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.pourquoidocteur.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, DS published at parent

Found

DNSKEY records
Yes (2)
DS at parent
Yes
Algorithms
RSASHA256 (8)
Key tags
23806, 45796
Signatures valid until
28 October 2026, 12:13 UTC

Checks

  • ✓ Signed, DS published at parent #8
    DNSSEC is enabled for this domain (DNSKEY and DS present), providing additional security for DNS lookups.
  • !
    Signatures expire in 151h0m0s
    DNSKEY signatures expire at 2026-10-28T12:13:06Z (in 151h0m0s). Check that re-signing works.
    #21

MX

warn

1 mail server

Found

PriorityHostRecordsReverse DNS
1mail2.pourquoidocteur.frA 5.135.61.66mail2.frequencem.com ✓

Checks

  • ✓ 1 MX record #9
    Found 1 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: mail2.pourquoidocteur.fr
    #11
  • !
    Single MX host, no backup
    Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • ✓ At most 5 MX records #13
    Found 1 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 1 MX address have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mail2.pourquoidocteur.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