texel.nl

Checked 22 October 2026, 16:31 UTC · via 8.8.8.8
!Passed with warnings
28 passed 4 warnings 0 failed 1 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:spf.mail-scanner.eu include:spf.protection.outlook.com include:_spf.services.centric.eu include:_spf.zorgmail.nl include:spf.pinkprivate.cloud include:spf_cluster.yard.nl include:spf_servers.yard.nl include:_spf.secudoc.app include:spf.shockmedia.email ip4:87.233.198.3 ip6:2001:9a8:a6:0:87:233:198:3 ip6:2A07:CB84:3075:912:10:10:159:25 ip6:2A07:CB81:3711:815:10:10:160:25 ip6:2001:9a8:0:112:87:233:230:114 ip4:82.151.55.146 ip4:145.131.250.189/27 ip4:185.8.52.254 ip4:185.8.53.254 ip4:176.74.239.242 ip4:213.208.232.101 ip4:87.233.230.114 -all
DNS lookups
10 of 10
Void lookups
0 of 2

Checks

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

pass

p=reject (_dmarc.texel.nl)

Found

Record
v=DMARC1; p=reject; rua=mailto:zsfdxpgd@ag.eu.dmarcadvisor.com; ruf=mailto:ruf@texel.nl
Found at
_dmarc.texel.nl
External report address
mailto:zsfdxpgd@ag.eu.dmarcadvisor.com (authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
ruamailto:zsfdxpgd@ag.eu.dmarcadvisor.comAggregate report addresses
rufmailto:ruf@texel.nlFailure report addresses

Checks

  • ✓ Policy: reject #4
    DMARC policy is set to 'reject', which provides the strongest protection against email spoofing.
  • ✓ 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.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:zsfdxpgd@ag.eu.dmarcadvisor.com
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: selector1, s1, s2

Found

Selectors
selector1, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
selector1RSA 2048 bits
s1RSA 2048 bits
s2RSA 1024 bits

Checks

  • ✓ Keys found: selector1, s1, s2 #7
    DKIM keys found for this domain with selectors: selector1, s1, s2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: s2 (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 (3)
DS at parent
Yes
Algorithms
RSASHA256 (8)
Key tags
37789, 55964, 8136
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
10texel-nl.p-v1.mx.microsoftA 52.101.185.114 A 52.101.209.31 A 52.101.91.162 A 52.101.73.120 AAAA 2a01:111:f403:ca04::4 AAAA 2a01:111:f403:ca3c::8 AAAA 2a01:111:f403:ca48::8 AAAA 2a01:111:f403:ca3c::amail-zrxpr04cu00102.inbound.protection.outlook.com ✓ mail-cpjpr05cu00207.inbound.protection.outlook.com ✓ mail-matpr04cu00302.inbound.protection.outlook.com ✓ mail-am7pr02cu00300.inbound.protection.outlook.com ✓ mail-db4pr02cu00204.inbound.protection.outlook.com ✓ mail-zrxpr05cu00100.inbound.protection.outlook.com ✓ mail-miypr02cu00100.inbound.protection.outlook.com ✓ mail-zrxpr07cu00102.inbound.protection.outlook.com ✓

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 8 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
texel-nl.p-v1.mx.microsoft2 0 1 ea7a25255d111fc3… 3 1 1 54883cc5f1849331… 3 1 1 803f7447cc75b208… 2 0 1 c1ad7778796d20bc… 3 1 1 cfd68bde4129c00a…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