vomar.nl

Checked 22 October 2026, 17:10 UTC · via 8.8.8.8
✗Problems found
24 passed 4 warnings 1 failed 1 info

SPF

pass

SPF record published

Found

Record
v=spf1 mx a include:_spf.anewspring.nl include:spf.afas.online include:spf.topdesk.net include:spf.protection.outlook.com include:isp-online.io ip4:185.254.40.1 ip4:185.254.40.232 ip4:149.210.133.131 -all
DNS lookups
8 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1; p=none; rua=mailto:rua@vomar.nl; ruf=mailto:rua@vomar.nl; pct=100
Found at
_dmarc.vomar.nl
TagValueMeaning
vDMARC1Version
pnonePolicy
pct100Percentage of mail the policy applies to
ruamailto:rua@vomar.nlAggregate report addresses
rufmailto:rua@vomar.nlFailure report addresses

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:rua@vomar.nl
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

warn

Selectors: dkim, selector1

Found

Selectors
dkim, selector1
_domainkey
NOERROR
SelectorKeyFlags
dkimRSA 1024 bitsh=sha256
selector1RSA 2048 bits

Checks

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

warn

Not signed

Found

DNSKEY records
No (0)
DS at parent
No

Checks

  • !
    Not enabled
    DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8

MX

pass

2 mail servers

Found

PriorityHostRecordsReverse DNS
10mx1.antispam-login.netA 93.94.228.132 A 93.94.228.133 AAAA 2a01:518:1:42:8::132 AAAA 2a01:518:1:42:8::133filter1.antispam-login.net ✓ filter2.antispam-login.net ✓ filter1.antispam-login.net ✓ filter2.antispam-login.net ✓
20mx2.antispam-login.netA 93.94.228.132 A 93.94.228.133 AAAA 2a01:518:1:42:8::133 AAAA 2a01:518:1:42:8::132filter1.antispam-login.net ✓ filter2.antispam-login.net ✓ filter2.antispam-login.net ✓ filter1.antispam-login.net ✓

Checks

  • ✓ 2 MX records #9
    Found 2 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 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 8 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx1.antispam-login.net3 1 1 1fdb1c74a3a6d6c5…Yes
mx2.antispam-login.net3 1 1 1fdb1c74a3a6d6c5…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 2 MX hosts 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