vip.nl

Checked 21 October 2026, 21:26 UTC · via 8.8.8.8
✗Problems found
22 passed 4 warnings 1 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:se.spf.provider.nl include:net.spf.provider.nl include:sendgrid.net include:spf.protection.outlook.com include:servers.mcsv.net include:ab.sendgrid.net ~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.vip.nl)

Found

Record
v=DMARC1; p=none; sp=none; rua=mailto:dmreport@vip.nl!10m; ruf=mailto:dmreport@vip.nl!10m; rf=afrf; pct=100; ri=86400;fo=1
Found at
_dmarc.vip.nl
TagValueMeaning
vDMARC1Version
pnonePolicy
spnoneSubdomain policy
pct100Percentage of mail the policy applies to
ruamailto:dmreport@vip.nl!10mAggregate report addresses
rufmailto:dmreport@vip.nl!10mFailure report addresses
fo1Failure reporting options
rfafrfFailure report format
ri86400Report interval (seconds)

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:dmreport@vip.nl!10m
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

warn

Selectors: default, k1, google

Found

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

Checks

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

warn

2 mail servers

Found

PriorityHostRecordsReverse DNS
5mx01.provider.nlA 138.201.223.76 A 144.76.235.114 A 138.201.35.78 A 138.201.223.70 A 144.76.235.113smtp04.mail.provider.nl ✓ smtp06.mail.provider.nl ✓ smtp08.mail.provider.nl ✓ smtp03.mail.provider.nl ✓ smtp05.mail.provider.nl ✓
10mx02.provider.nlA 138.201.223.76 A 138.201.35.78 A 138.201.223.70 A 144.76.235.113 A 144.76.235.114smtp04.mail.provider.nl ✓ smtp08.mail.provider.nl ✓ smtp03.mail.provider.nl ✓ smtp05.mail.provider.nl ✓ smtp06.mail.provider.nl ✓

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: mx01.provider.nl, mx02.provider.nl
    #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 10 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx01.provider.nlnone-
mx02.provider.nlnone-

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

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