tinbergen.nl

Checked 22 October 2026, 16:32 UTC · via 8.8.8.8
!Passed with warnings
26 passed 6 warnings 0 failed 1 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:spf.protection.outlook.com include:spf.eprov.nl ip4:178.22.57.73 ~all
DNS lookups
2 of 10
Void lookups
0 of 2

Checks

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

warn

p=quarantine (_dmarc.tinbergen.nl)

Found

Record
v=DMARC1; p=quarantine; sp=quarantine; rua=mailto:dmarc@2y0adusw.uriports.com; ruf=mailto:dmarc@2y0adusw.uriports.com; fo=1:d:s
Found at
_dmarc.tinbergen.nl
External report address
mailto:dmarc@2y0adusw.uriports.com (authorized)
TagValueMeaning
vDMARC1Version
pquarantinePolicy
spquarantineSubdomain policy
ruamailto:dmarc@2y0adusw.uriports.comAggregate report addresses
rufmailto:dmarc@2y0adusw.uriports.comFailure report addresses
fo1:d:sFailure reporting options

Checks

  • !
    Policy: quarantine
    DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • ✓ 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:dmarc@2y0adusw.uriports.com
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: k1, selector1, selector2, s1, s2

Found

Selectors
k1, selector1, selector2, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
k1RSA 1024 bits
selector1RSA 2048 bits
selector2RSA 2048 bits
s1RSA 2048 bits
s2RSA 1024 bits

Checks

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

warn

Signed, DS published at parent

Found

DNSKEY records
Yes (4)
DS at parent
Yes
Algorithms
RSASHA256 (8)
Key tags
35409, 41806, 42812, 18403
Signatures valid until
26 October 2026, 15:55 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 expire in 95h0m0s
    DNSKEY signatures expire at 2026-10-26T15:55:51Z (in 95h0m0s). Check that re-signing works.
    #21

MX

warn

1 mail server

Found

PriorityHostRecordsReverse DNS
0tinbergen-nl.u-v1.mx.microsoftA 52.101.103.36 A 52.101.68.39 A 52.101.68.27 A 52.101.68.12 AAAA 2a01:111:f403:ca21::8 AAAA 2a01:111:f403:ca21::c AAAA 2a01:111:f403:ca04::4 AAAA 2a01:111:f403:ca3c::6mail-miypr05cu00104.inbound.protection.outlook.com ✓ mail-db7pr03cu00607.inbound.protection.outlook.com ✓ mail-db7pr03cu00503.inbound.protection.outlook.com ✓ mail-db9pr02cu00204.inbound.protection.outlook.com ✓ mail-matpr04cu00100.inbound.protection.outlook.com ✓ mail-matpr04cu00204.inbound.protection.outlook.com ✓ mail-db4pr02cu00204.inbound.protection.outlook.com ✓ mail-zrxpr04cu00106.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
tinbergen-nl.u-v1.mx.microsoft2 0 1 c1ad7778796d20bc… 3 1 1 cfd68bde4129c00a… 3 1 1 54883cc5f1849331… 3 1 1 803f7447cc75b208… 2 0 1 ea7a25255d111fc3…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