samangroep.nl

p=quarantine (_dmarc.samangroep.nl)

Found

Record

v=DMARC1; p=quarantine; aspf=r; rua=mailto:626a5f41e44cd@ag.dmarcly.com; ruf=mailto:626a5f41e44cd@fo.dmarcly.com; sp=quarantine; fo=0;

Found at

_dmarc.samangroep.nl

External report address

mailto:626a5f41e44cd@ag.dmarcly.com (authorized)

External report address

mailto:626a5f41e44cd@fo.dmarcly.com (authorized)

Checks

• !

  Policy: quarantine

  DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.

  #4
• ✓ 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.
• ✓ Aggregate reports enabled #19

  Aggregate reports are sent to: mailto:626a5f41e44cd@ag.dmarcly.com
• ✓ Subdomain policy: quarantine #20

  Subdomains are covered by policy 'quarantine'.
• ✓ External report addresses authorized #29

  Report addresses in other domains have published their authorization.

Selectors: selector1, selector2

Found

Selectors

selector1, selector2

_domainkey

NOERROR

Checks

• ✓ Keys found: selector1, selector2 #7

  DKIM keys found for this domain with selectors: selector1, selector2
• !

  1024-bit DKIM key

  1024-bit RSA keys are the minimum and are considered weak today: selector1 (1024 bits), selector2 (1024 bits). Rotate to a 2048-bit key.

  #23
• ✓ No problematic flags #24

  No keys in test mode, revoked, or limited to SHA-1.

Signed, but no DS at parent

Found

DNSKEY records

Yes (2)

DS at parent

No

Algorithms

ECDSAP256SHA256 (13)

Key tags

34505, 2371

Signatures valid until

14 December 2026, 11:57 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-12-14 #21

  DNSKEY signatures are valid until 2026-12-14T11:57:02Z.

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: mx1-eu1.ppe-hosted.com, mx2-eu1.ppe-hosted.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 4 MX addresss have a PTR record that resolves back to them.

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