bamboo.fr

Checked 22 October 2026, 01:52 UTC · via 8.8.8.8
✗Problems found
23 passed 4 warnings 1 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:_spf.google.com include:spf.mailjet.com include:_mailcust.gandi.net include:spf.brevo.com ~all
DNS lookups
5 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 5 of 10 DNS lookups #2
    SPF record needs 5 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.bamboo.fr)

Found

Record
v=DMARC1; p=none; rua=mailto:support.informatique@bamboo.fr,mailto:rua@dmarc.brevo.com; ruf=mailto:support.informatique@bamboo.fr; fo=1; sp=none; aspf=r
Found at
_dmarc.bamboo.fr
External report address
mailto:rua@dmarc.brevo.com (authorized)
TagValueMeaning
vDMARC1Version
pnonePolicy
spnoneSubdomain policy
ruamailto:support.informatique@bamboo.fr,mailto:rua@dmarc.brevo.comAggregate report addresses
rufmailto:support.informatique@bamboo.frFailure report addresses
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.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:support.informatique@bamboo.fr, mailto:rua@dmarc.brevo.com
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: mail, google

Found

Selectors
mail, google
_domainkey
NOERROR
SelectorKeyFlags
mailRSA 1024 bits
googleRSA 2048 bits

Checks

  • ✓ Keys found: mail, google #7
    DKIM keys found for this domain with selectors: mail, google
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: mail (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

pass

Signed, DS published at parent

Found

DNSKEY records
Yes (1)
DS at parent
Yes
Algorithms
ECDSAP256SHA256 (13)
Key tags
49328
Signatures valid until
5 November 2026, 00:00 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 valid until 2026-11-05 #21
    DNSKEY signatures are valid until 2026-11-05T00:00:00Z.

MX

warn

8 mail servers

Found

PriorityHostRecordsReverse DNS
0MAIL.DATADAM.frA 51.91.186.254mail.datadam.fr ✓
1ASPMX.L.GOOGLE.COMA 142.251.127.27 AAAA 2a00:1450:4001:c21::1alcfrai-in-f27.1e100.net ✓ lcfrai-in-f26.1e100.net ✓
3ALT1.ASPMX.L.GOOGLE.COMA 142.250.147.27 AAAA 2a00:1450:4025:c01::1ard-in-f27.1e100.net ✓ rd-in-f26.1e100.net ✓
3ALT2.ASPMX.L.GOOGLE.COMA 172.253.152.27 AAAA 2a00:1450:4010:c22::1byulpptr-in-f27.1e100.net ✓ yulpptr-in-f27.1e100.net ✓
5ASPMX2.GOOGLEMAIL.COMA 142.250.147.26 AAAA 2a00:1450:4025:c01::1brd-in-f26.1e100.net ✓ rd-in-f27.1e100.net ✓
5ASPMX3.GOOGLEMAIL.COMA 172.253.152.26 AAAA 2a00:1450:4010:c22::1byulpptr-in-f26.1e100.net ✓ yulpptr-in-f27.1e100.net ✓
5ASPMX4.GOOGLEMAIL.COMA 192.179.20.26 AAAA 2404:6800:4000:1027::1bncboms-in-f26.1e100.net ✓ ncboms-in-f27.1e100.net ✓
5ASPMX5.GOOGLEMAIL.COMA 192.178.158.27 AAAA 2404:6800:4013:813::1alcdels-in-f27.1e100.net ✓ lcdels-in-f26.1e100.net ✓

Checks

  • ✓ 8 MX records #9
    Found 8 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: MAIL.DATADAM.fr
    #11
  • ✓ Redundant MX hosts #12
    Found 8 MX records, which provides redundancy for email delivery.
  • !
    More than 5 MX records
    Found 8 MX records, which is more than the recommended maximum of 5. Too many MX records may indicate a misconfiguration.
    #13
  • ✓ 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 15 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
MAIL.DATADAM.frnone-
ASPMX.L.GOOGLE.COMnone-
ALT1.ASPMX.L.GOOGLE.COMnone-
ALT2.ASPMX.L.GOOGLE.COMnone-
ASPMX2.GOOGLEMAIL.COMnone-
ASPMX3.GOOGLEMAIL.COMnone-
ASPMX4.GOOGLEMAIL.COMnone-
ASPMX5.GOOGLEMAIL.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