punt.nl

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

SPF

pass

SPF record published

Found

Record
v=spf1 a mx include:spf.mijndomeinhosting.nl ~all
DNS lookups
6 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1; p=none; sp=none; pct=100; adkim=r; aspf=r; rua=mailto:dmarc@reportdmarc.nl; rf=afrf; fo=0; ri=86400
Found at
_dmarc.punt.nl
External report address
mailto:dmarc@reportdmarc.nl (authorized)
TagValueMeaning
vDMARC1Version
pnonePolicy
spnoneSubdomain policy
pct100Percentage of mail the policy applies to
ruamailto:dmarc@reportdmarc.nlAggregate report addresses
adkimrDKIM alignment (r = relaxed, s = strict)
aspfrSPF alignment (r = relaxed, s = strict)
fo0Failure 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:dmarc@reportdmarc.nl
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

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 (1)
DS at parent
Yes
Algorithms
ECDSAP256SHA256 (13)
Key tags
59362
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

pass

2 mail servers

Found

PriorityHostRecordsReverse DNS
5mx1.mijndomein.nlA 185.233.34.27 A 185.233.34.19 A 185.233.34.153 AAAA 2a10:de80:1:4091:b9e9:221b:0:1 AAAA 2a10:de80:1:4092:b9e9:2299:0:1 AAAA 2a10:de80:1:4091:b9e9:2213:0:1mx1.mijndomein.nl ✓ mx1.mijndomein.nl ✓ mx1.mijndomein.nl ✓ mx1.mijndomein.nl ✓ mx1.mijndomein.nl ✓ mx1.mijndomein.nl ✓
6mx2.mijndomein.nlA 185.233.34.28 A 185.233.34.154 A 185.233.34.147 AAAA 2a10:de80:1:4092:b9e9:2293:0:1 AAAA 2a10:de80:1:4091:b9e9:221c:0:1 AAAA 2a10:de80:1:4092:b9e9:229a:0:1mx2.mijndomein.nl ✓ mx2.mijndomein.nl ✓ mx2.mijndomein.nl ✓ mx2.mijndomein.nl ✓ mx2.mijndomein.nl ✓ mx2.mijndomein.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.
  • ✓ 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 12 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.mijndomein.nl3 1 1 6a0e54ead97d1bb1… 3 1 1 eff81dacdb4d6d4e… 3 1 1 beb1e3316f045791…Yes
mx2.mijndomein.nl3 1 1 6d87b163ab8d4868… 3 1 1 6a0e54ead97d1bb1… 3 1 1 eff81dacdb4d6d4e…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