utwente.nl

Checked 21 October 2026, 21:26 UTC · via 8.8.8.8
!Passed with warnings
26 passed 4 warnings 0 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 mx a:smtppool.utwente.nl ip4:52.17.45.98 ip4:52.16.190.81 ip4:54.229.2.165 ip4:52.30.130.201 ip4:34.252.12.130 ip4:52.30.8.165 a:edgepool.ad.utwente.nl include:spf.protection.outlook.com ip4:159.183.231.20 -all
DNS lookups
4 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 4 of 10 DNS lookups #2
    SPF record needs 4 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=reject (_dmarc.utwente.nl)

Found

Record
v=DMARC1; p=reject; sp=none; fo=s; ri=3600; rua=mailto:dmarc@utwente.nl; ruf=mailto:dmarc+ruf@utwente.nl
Found at
_dmarc.utwente.nl
TagValueMeaning
vDMARC1Version
prejectPolicy
spnoneSubdomain policy
ruamailto:dmarc@utwente.nlAggregate report addresses
rufmailto:dmarc+ruf@utwente.nlFailure report addresses
fosFailure reporting options
ri3600Report interval (seconds)

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:dmarc@utwente.nl
  • !
    Subdomains unprotected (sp=none)
    DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.
    #20
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

warn

Selectors: mail, selector1, selector2

Found

Selectors
mail, selector1, selector2
_domainkey
NOERROR
SelectorKeyFlags
mailRSA 2048 bits
selector1RSA 1024 bits
selector2RSA 2048 bits

Checks

  • ✓ Keys found: mail, selector1, selector2 #7
    DKIM keys found for this domain with selectors: mail, selector1, selector2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: selector1 (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
17944, 46341, 12285
Signatures valid until
17 November 2026, 22:58 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-17 #21
    DNSKEY signatures are valid until 2026-11-17T22:58:23Z.

MX

warn

1 mail server

Found

PriorityHostRecordsReverse DNS
10utwente-nl.mail.protection.outlook.comA 52.101.68.8 A 52.101.181.153 A 52.101.68.15 A 52.101.91.162 AAAA 2a01:111:f403:ca48::e AAAA 2a01:111:f403:ca21::e AAAA 2a01:111:f403:ca48::a AAAA 2a01:111:f403:c967::amail-du0pr03cu00100.inbound.protection.outlook.com ✓ mail-wa4pr04cu00101.inbound.protection.outlook.com ✓ mail-db6pr03cu00107.inbound.protection.outlook.com ✓ mail-matpr04cu00302.inbound.protection.outlook.com ✓ mail-miypr03cu00206.inbound.protection.outlook.com ✓ mail-matpr04cu00306.inbound.protection.outlook.com ✓ mail-miypr02cu00202.inbound.protection.outlook.com ✓ mail-cpjpr05cu00102.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 0 of 1 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
utwente-nl.mail.protection.outlook.comnone-

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