tvd.be

p=reject (_dmarc.tvd.be)

Found

Record

v=DMARC1; p=reject

Found at

_dmarc.tvd.be

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'.

No keys found under the checked selectors

Found

Selectors

None found

_domainkey

NOERROR

Checks

• !

  No key under common selectors

  The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.

  #7

Signed, but no DS at parent

Found

DNSKEY records

Yes (1)

DS at parent

No

Algorithms

RSASHA256 (8)

Key tags

581

Signatures valid until

5 November 2026, 00:00 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-05 #21

  DNSKEY signatures are valid until 2026-11-05T00:00:00Z.

2 mail servers

Found

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: mx186.m2bp.com, mx186.mb1p.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.
• !

  Addresses without reverse DNS

  These MX addresses have no PTR record, which many receivers treat as a spam signal: 164.90.197.143 (mx186.m2bp.com), 147.182.189.184 (mx186.m2bp.com), 164.90.197.79 (mx186.m2bp.com), 147.182.160.18 (mx186.m2bp.com), 164.90.197.105 (mx186.m2bp.com), 147.182.130.78 (mx186.m2bp.com), 164.90.197.162 (mx186.m2bp.com), 147.182.180.139 (mx186.m2bp.com), 147.182.160.18 (mx186.mb1p.com), 164.90.197.162 (mx186.mb1p.com), 164.90.197.105 (mx186.mb1p.com), 164.90.197.143 (mx186.mb1p.com), 147.182.130.78 (mx186.mb1p.com), 147.182.189.184 (mx186.mb1p.com), 164.90.197.79 (mx186.mb1p.com), 147.182.180.139 (mx186.mb1p.com). Ask your hosting provider to set one.

  #30

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

Found

DANE (TLSA records)

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