evlks.de

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

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:178.249.31.123 ip4:157.97.45.68 ip4:185.221.107.223 ip4:85.13.150.237 ip4:62.245.164.64/27 ip4:212.114.243.93 ip4:212.114.243.94 ip4:116.202.184.120 ip4:188.34.202.145 ip4:116.203.101.27 ip4:178.249.31.122 ip4:91.90.167.93 include:_spf.expurgate.net include:spf.protection.outlook.com include:agenturserver.de include:_spf.sendnode.com include:_spf.zimpel.de a:j334495.servers.jiffybox.net a:idm.evlks.daasi.de a:mx05.produktiv-tech.de -all
DNS lookups
8 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1; p=none
Found at
_dmarc.evlks.de
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
ECDSAP256SHA256 (13)
Key tags
51783, 37403
Signatures valid until
31 October 2026, 10:48 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-31 #21
    DNSKEY signatures are valid until 2026-10-31T10:48:05Z.

MX

warn

1 mail server

Found

PriorityHostRecordsReverse DNS
10mxtls.expurgate.netA 195.190.135.123 A 194.145.224.124 A 195.190.135.124 A 194.145.224.125 A 194.145.224.120 A 195.190.135.120 A 194.145.224.121 A 195.190.135.122 A 194.145.224.122 A 194.145.224.123 A 195.190.135.121 A 195.190.135.125mxtls.expurgate.net ✓ mxtls.expurgate.net ✓ mxtls.expurgate.net ✓ mxtls.expurgate.net ✓ mxtls.expurgate.net ✓ mxtls.expurgate.net ✓ mxtls.expurgate.net ✓ mxtls.expurgate.net ✓ mxtls.expurgate.net ✓ mxtls.expurgate.net ✓ mxtls.expurgate.net ✓ mxtls.expurgate.net ✓

Checks

  • ✓ 1 MX record #9
    Found 1 MX records for this domain.
  • ✓ All hosts resolve #10
    All MX records resolve to valid IP addresses.
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: mxtls.expurgate.net
    #11
  • !
    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 12 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
mxtls.expurgate.netnone-

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