kivi.nl

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

SPF

fail

SPF record published

Found

Record
v=spf1 a mx ip4:37.97.155.113 ip4:213.125.235.237 ip4:198.37.154.7 ip4:145.103.247.251 ip4:145.103.247.248 ip4:213.125.235.235 ip4:31.14.97.198 ip4:185.53.162.117 ip4:185.250.239.5 ip4:149.210.155.245 ip4:161.38.204.222 ip6:2a01:7c8:aabf:552::1/48 include:spf.bhosted.nl include:spf.dynect.net include:_spf.exactonline.nl include:spf.protection.outlook.com include:_spf.argewebhosting.nl include:mailgun.org include:_spf.e-boekhouden.nl ~all
DNS lookups
15 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✗
    15 DNS lookups, over the limit of 10
    SPF record needs 15 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record.
    #2
  • ✓ 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.kivi.nl)

Found

Record
v=DMARC1; p=none
Found at
_dmarc.kivi.nl
TagValueMeaning
vDMARC1Version
pnonePolicy

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.
  • !
    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

DKIM

warn

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NOERROR

Checks

  • !
    No key under common selectors
    The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7

DNSSEC

pass

Signed, DS published at parent

Found

DNSKEY records
Yes (2)
DS at parent
Yes
Algorithms
RSASHA256 (8)
Key tags
35257, 48834
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
10mx.bhosted.nlA 94.124.121.10 A 94.124.121.32 A 94.124.121.12 AAAA 2a02:9e0:8000::10 AAAA 2a02:9e0:8000::32 AAAA 2a02:9e0:8000::12mx01.bhosted.nl ✓ mx03.bhosted.nl ✓ mx02.bhosted.nl ✓ mx01.bhosted.nl ✓ mx03.bhosted.nl ✓ mx02.bhosted.nl ✓

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 6 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
mx.bhosted.nl3 1 1 d134e2d232b61ac9… 3 1 1 43e936a2116f0191…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