geekzone.fr

Checked 22 October 2026, 03:12 UTC · via 8.8.8.8
!Passed with warnings
24 passed 4 warnings 0 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 a mx ip4:163.172.108.19 ip6:fe80::ec4:7aff:fe86:39de include:spf.messagingengine.com ~all
DNS lookups
3 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 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

warn

p=reject (_dmarc.geekzone.fr)

Found

Record
v=DMARC1; p=reject;
Found at
_dmarc.geekzone.fr
TagValueMeaning
vDMARC1Version
prejectPolicy

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.
  • !
    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
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.

DKIM

pass

Selectors: mail

Found

Selectors
mail
_domainkey
NOERROR
SelectorKeyFlags
mailRSA 2048 bits

Checks

  • ✓ Keys found: mail #7
    DKIM keys found for this domain with selectors: mail
  • ✓ Strong keys #23
    DKIM keys are strong enough: mail: RSA 2048 bits.
  • ✓ No problematic flags #24
    No keys in test mode, revoked, or limited to SHA-1.

DNSSEC

warn

Not signed

Found

DNSKEY records
No (0)
DS at parent
No

Checks

  • !
    Not enabled
    DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8

MX

warn

2 mail servers

Found

PriorityHostRecordsReverse DNS
10in1-smtp.messagingengine.comA 103.168.172.220 A 103.168.172.223 A 103.168.172.216 A 103.168.172.217 A 103.168.172.221 A 103.168.172.219 A 103.168.172.222 A 103.168.172.218phl-mx-05.messagingengine.com ✓ phl-mx-08.messagingengine.com ✓ phl-mx-01.messagingengine.com ✓ phl-mx-02.messagingengine.com ✓ phl-mx-06.messagingengine.com ✓ phl-mx-04.messagingengine.com ✓ phl-mx-07.messagingengine.com ✓ phl-mx-03.messagingengine.com ✓
20in2-smtp.messagingengine.comA 202.12.124.217 A 202.12.124.218 A 202.12.124.216 A 202.12.124.219stl-mx-02.messagingengine.com ✓ stl-mx-03.messagingengine.com ✓ stl-mx-01.messagingengine.com ✓ stl-mx-04.messagingengine.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: in1-smtp.messagingengine.com, in2-smtp.messagingengine.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 12 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
in1-smtp.messagingengine.comnone-
in2-smtp.messagingengine.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