pixum.de

Checked 21 October 2026, 23:50 UTC · via 8.8.8.8
✗Problems found
17 passed 4 warnings 1 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:93.191.160.0/21 include:_spf.google.com mx ~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

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

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
40, 31942
Signatures valid until
11 November 2026, 00:06 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-11 #21
    DNSKEY signatures are valid until 2026-11-11T00:06:43Z.

MX

warn

11 mail servers

Found

PriorityHostRecordsReverse DNS
10aspmx.l.google.comA 142.251.127.26 AAAA 2a00:1450:4001:c21::1alcfrai-in-f26.1e100.net ✓ lcfrai-in-f26.1e100.net ✓
20alt1.aspmx.l.google.comA 142.250.147.26 AAAA 2a00:1450:4025:c01::1ard-in-f26.1e100.net ✓ rd-in-f26.1e100.net ✓
20alt2.aspmx.l.google.comA 172.253.152.26 AAAA 2a00:1450:4010:c22::1ayulpptr-in-f26.1e100.net ✓ yulpptr-in-f26.1e100.net ✓
30aspmx2.googlemail.comA 142.250.147.26 AAAA 2a00:1450:4025:c01::1ard-in-f26.1e100.net ✓ rd-in-f26.1e100.net ✓
30aspmx3.googlemail.comA 172.253.152.27 AAAA 2a00:1450:4010:c22::1ayulpptr-in-f27.1e100.net ✓ yulpptr-in-f26.1e100.net ✓
30aspmx4.googlemail.comA 192.179.20.27 AAAA 2404:6800:4000:1027::1ancboms-in-f27.1e100.net ✓ ncboms-in-f26.1e100.net ✓
30aspmx5.googlemail.comA 192.178.158.27 AAAA 2404:6800:4013:813::1alcdels-in-f27.1e100.net ✓ lcdels-in-f26.1e100.net ✓
40mx01.hornetsecurity.comA 94.100.132.8mx01.hornetsecurity.com ✓
41mx02.hornetsecurity.comA 94.100.136.8mx02.hornetsecurity.com ✓
42mx03.hornetsecurity.comA 94.100.134.8mx03.hornetsecurity.com ✓
43mx04.hornetsecurity.comA 94.100.136.7mx04.hornetsecurity.com ✓

Checks

  • ✓ 11 MX records #9
    Found 11 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: mx01.hornetsecurity.com, mx02.hornetsecurity.com, mx03.hornetsecurity.com, mx04.hornetsecurity.com
    #11
  • ✓ Redundant MX hosts #12
    Found 11 MX records, which provides redundancy for email delivery.
  • !
    More than 5 MX records
    Found 11 MX records, which is more than the recommended maximum of 5. Too many MX records may indicate a misconfiguration.
    #13
  • ✓ 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 18 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
aspmx.l.google.comnone-
alt1.aspmx.l.google.comnone-
alt2.aspmx.l.google.comnone-
aspmx2.googlemail.comnone-
aspmx3.googlemail.comnone-
aspmx4.googlemail.comnone-
aspmx5.googlemail.comnone-
mx01.hornetsecurity.comnone-
mx02.hornetsecurity.comnone-
mx03.hornetsecurity.comnone-
mx04.hornetsecurity.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