jurarat.de

Checked 21 October 2026, 23:02 UTC · via 8.8.8.8
✗Problems found
16 passed 3 warnings 2 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:spf.improvmx.com ~all
DNS lookups
1 of 10
Void lookups
0 of 2

Checks

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

No DMARC record found

Checks

  • ✗
    No DMARC record
    No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.
    #5

DKIM

fail

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NXDOMAIN

Checks

  • ✗
    No DKIM keys published
    _domainkey.jurarat.de does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7

DNSSEC

warn

Not signed

Found

DNSKEY records
No (0)
DS at parent
No

Checks

  • !
    Not enabled
    DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8

MX

warn

2 mail servers

Found

PriorityHostRecordsReverse DNS
10mx1.improvmx.comA 35.181.18.45 A 13.37.195.136 A 15.236.236.160 AAAA 2a05:d012:412:e201:88aa:e7b9:7a43:12d7 AAAA 2a05:d012:412:e202:f36:2c1f:1a49:d38a AAAA 2a05:d012:412:e203:373a:f51a:4a85:1d25ec2-35-181-18-45.eu-west-3.compute.amazonaws.com ✓ ec2-13-37-195-136.eu-west-3.compute.amazonaws.com ✓ ec2-15-236-236-160.eu-west-3.compute.amazonaws.com ✓ no PTR no PTR no PTR
20mx2.improvmx.comA 15.236.61.92 A 13.36.222.39 A 13.36.107.63 AAAA 2a05:d012:412:e202:e81e:cc44:3b53:8a3d AAAA 2a05:d012:412:e201:1f6e:f6e4:8fd7:4678 AAAA 2a05:d012:412:e203:7e33:3d9c:28d7:ee20ec2-15-236-61-92.eu-west-3.compute.amazonaws.com ✓ ec2-13-36-222-39.eu-west-3.compute.amazonaws.com ✓ ec2-13-36-107-63.eu-west-3.compute.amazonaws.com ✓ no PTR no PTR no PTR

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.
  • !
    Addresses without reverse DNS
    These MX addresses have no PTR record, which many receivers treat as a spam signal: 2a05:d012:412:e201:88aa:e7b9:7a43:12d7 (mx1.improvmx.com), 2a05:d012:412:e202:f36:2c1f:1a49:d38a (mx1.improvmx.com), 2a05:d012:412:e203:373a:f51a:4a85:1d25 (mx1.improvmx.com), 2a05:d012:412:e202:e81e:cc44:3b53:8a3d (mx2.improvmx.com), 2a05:d012:412:e201:1f6e:f6e4:8fd7:4678 (mx2.improvmx.com), 2a05:d012:412:e203:7e33:3d9c:28d7:ee20 (mx2.improvmx.com). Ask your hosting provider to set one.
    #30

TLS

warn

no MTA-STS · no TLS-RPT · DANE on 0 of 2 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx1.improvmx.comnone-
mx2.improvmx.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