metaalunie.nl

Checked 22 October 2026, 14:31 UTC · via 8.8.8.8
✗Problems found
24 passed 5 warnings 1 failed 1 info

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:92.70.147.49/28 ip4:205.201.128.0/20 ip4:198.2.128.0/18 ip4:85.146.240.186 ip4:31.7.7.155 ip4:161.51.82.74 ip4:141.138.139.241 ip4:37.97.247.235 include:spf.protection.outlook.com include:spf.zaalagenda.nl include:_spf.smtp.mailtrap.live a:mx1.anywise.net a:mx5.anywise.net include:servers.mcsv.net -all
DNS lookups
7 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1; p=none; rua=mailto:dmarc@smtp.mailtrap.live; ruf=mailto:dmarc@smtp.mailtrap.live; rf=afrf; pct=100
Found at
_dmarc.metaalunie.nl
External report address
mailto:dmarc@smtp.mailtrap.live (not authorized)
TagValueMeaning
vDMARC1Version
pnonePolicy
pct100Percentage of mail the policy applies to
ruamailto:dmarc@smtp.mailtrap.liveAggregate report addresses
rufmailto:dmarc@smtp.mailtrap.liveFailure report addresses
rfafrfFailure report format

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:dmarc@smtp.mailtrap.live
  • !
    Report address not authorized
    These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:dmarc@smtp.mailtrap.live (needs metaalunie.nl._report._dmarc.smtp.mailtrap.live). Ask the report provider to publish the record, or check the address.
    #29

DKIM

warn

Selectors: selector1, selector2

Found

Selectors
selector1, selector2
_domainkey
NOERROR
SelectorKeyFlags
selector1RSA 2048 bits
selector2RSA 1024 bits

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

DNSSEC

pass

Signed, DS published at parent

Found

DNSKEY records
Yes (2)
DS at parent
Yes
Algorithms
RSASHA256 (8)
Key tags
22104, 16711
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

1 mail server

Found

PriorityHostRecordsReverse DNS
0metaalunie-nl.f-v1.mx.microsoftA 52.101.68.39 A 52.101.103.143 A 52.101.68.25 A 52.101.209.28 AAAA 2a01:111:f403:ca09::28 AAAA 2a01:111:f403:ca3c::a AAAA 2a01:111:f403:ca09::24 AAAA 2a01:111:f403:ca09::22mail-db7pr03cu00607.inbound.protection.outlook.com ✓ mail-miypr03cu00107.inbound.protection.outlook.com ✓ mail-db8pr02cu00101.inbound.protection.outlook.com ✓ mail-cpjpr05cu00104.inbound.protection.outlook.com ✓ mail-am6pr02cu00300.inbound.protection.outlook.com ✓ mail-zrxpr07cu00102.inbound.protection.outlook.com ✓ mail-am6pr02cu00204.inbound.protection.outlook.com ✓ mail-am7pr02cu00302.inbound.protection.outlook.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.
  • ✓ All hosts have IPv6 #11
    All MX records resolve to IPv6 addresses.
  • !
    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 8 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
metaalunie-nl.f-v1.mx.microsoft3 1 1 54883cc5f1849331… 2 0 1 ea7a25255d111fc3… 2 0 1 c1ad7778796d20bc… 3 1 1 803f7447cc75b208… 3 1 1 cfd68bde4129c00a…Yes

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
  • !
    Not configured
    MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".
    #35
  • ✓ DANE on all MX hosts #36
    All 1 MX host publish DNSSEC-validated TLSA records.

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