iex.nl

Checked 21 October 2026, 21:22 UTC · via 8.8.8.8
!Passed with warnings
25 passed 6 warnings 0 failed 2 info

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:212.7.205.120/30 include:_spf.google.com -all
DNS lookups
1 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1;p=quarantine;
Found at
_dmarc.iex.nl
TagValueMeaning
vDMARC1Version
pquarantinePolicy

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

DKIM

warn

Selectors: default, google

Found

Selectors
default, google
_domainkey
NOERROR
SelectorKeyFlags
defaultRSA 1024 bits
googleRSA 2048 bits

Checks

  • ✓ Keys found: default, google #7
    DKIM keys found for this domain with selectors: default, google
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: default (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
40693, 43135
Signatures valid until
29 October 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-10-29 #21
    DNSKEY signatures are valid until 2026-10-29T00:00:00Z.

MX

warn

6 mail servers

Found

PriorityHostRecordsReverse DNS
10aspmx.l.google.comA 142.251.127.27 AAAA 2a00:1450:4001:c21::1blcfrai-in-f27.1e100.net ✓ lcfrai-in-f27.1e100.net ✓
20alt1.aspmx.l.google.comA 142.250.147.27 AAAA 2a00:1450:4025:c01::1brd-in-f27.1e100.net ✓ rd-in-f27.1e100.net ✓
20alt2.aspmx.l.google.comA 172.253.152.26 AAAA 2a00:1450:4010:c22::1byulpptr-in-f26.1e100.net ✓ yulpptr-in-f27.1e100.net ✓
30alt2.aspmx.l.google.comA 172.253.152.26 AAAA 2a00:1450:4010:c22::1byulpptr-in-f26.1e100.net ✓ yulpptr-in-f27.1e100.net ✓
30alt3.aspmx.l.google.comA 192.179.20.27 AAAA 2404:6800:4000:1027::1ancboms-in-f27.1e100.net ✓ ncboms-in-f26.1e100.net ✓
30alt4.aspmx.l.google.comA 192.178.158.26 AAAA 2404:6800:4013:813::1blcdels-in-f26.1e100.net ✓ lcdels-in-f27.1e100.net ✓

Checks

  • ✓ 6 MX records #9
    Found 6 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.
  • ✓ Redundant MX hosts #12
    Found 6 MX records, which provides redundancy for email delivery.
  • !
    More than 5 MX records
    Found 6 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 12 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
aspmx.l.google.comnone-
alt1.aspmx.l.google.comnone-
alt2.aspmx.l.google.comnone-
alt3.aspmx.l.google.comnone-
alt4.aspmx.l.google.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

warn

https://img.iex.nl/IEX.nl/images/bimi/bimi-svg-tiny-12-ps.svg

Found

Record
v=BIMI1;l=https://img.iex.nl/IEX.nl/images/bimi/bimi-svg-tiny-12-ps.svg;
Found at
default._bimi.iex.nl
Logo
https://img.iex.nl/IEX.nl/images/bimi/bimi-svg-tiny-12-ps.svg

Checks

  • !
    No certificate (a=)
    The logo is published without a Verified Mark Certificate. Gmail and Apple Mail only show BIMI logos with a VMC or CMC; Yahoo shows it without one.
    #38
  • ✓ DMARC meets BIMI requirements #39
    DMARC is enforced on all mail, as BIMI requires.