hagebau.de

Checked 21 October 2026, 22:41 UTC · via 8.8.8.8
✗Problems found
21 passed 6 warnings 1 failed 1 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:spf.hagebau.cloud ip4:217.237.163.0/27 ip4:217.237.163.32/27 ip4:217.6.38.0/26 ip4:62.153.229.224/27 ip4:194.233.195.188 ip4:194.233.195.189 ip4:195.206.137.107 ip4:195.206.137.108 ip4:195.206.137.111 ip4:81.18.106.0/24 ip4:81.18.105.0/24 ip4:194.233.195.190 ip4:195.179.119.240 ip4:80.85.192.0/20 ip4:194.233.195.188 ip4:194.233.195.189 ip4:195.206.137.72 ip4:195.206.137.107 ip4:195.206.137.108 ip4:195.206.137.111 ip4:195.206.137.57 ip4:195.206.137.19 ip4:195.206.137.56 ip4:185.124.243.178 ip4:45.132.68.54 include:antispameurope.com include:spf.mandrillapp.com -all
DNS lookups
5 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1; p=none; rua=mailto:dmarc-analyse@hagebau.com; ruf=mailto:dmarc-analyse@hagebau.com; fo=1; pct=100
Found at
_dmarc.hagebau.de
External report address
mailto:dmarc-analyse@hagebau.com (not authorized)
TagValueMeaning
vDMARC1Version
pnonePolicy
pct100Percentage of mail the policy applies to
ruamailto:dmarc-analyse@hagebau.comAggregate report addresses
rufmailto:dmarc-analyse@hagebau.comFailure report addresses
fo1Failure reporting options

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.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:dmarc-analyse@hagebau.com
  • !
    Report address not authorized
    These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:dmarc-analyse@hagebau.com (needs hagebau.de._report._dmarc.hagebau.com). Ask the report provider to publish the record, or check the address.
    #29

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
34505, 2371
Signatures valid until
9 December 2026, 11:56 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-12-09 #21
    DNSKEY signatures are valid until 2026-12-09T11:56:31Z.

MX

warn

1 mail server

Found

PriorityHostRecordsReverse DNS
10hagebau-com.mail.cloud.nospamproxy.comA 178.212.92.112 A 193.37.132.187de-s119-gw2.mail.cloud.nospamproxy.com ✓ de-s119-gw1.mail.cloud.nospamproxy.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.
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: hagebau-com.mail.cloud.nospamproxy.com
    #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 2 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
hagebau-com.mail.cloud.nospamproxy.com3 1 1 897f916ec02bfb38… 3 1 1 15987f49fc954bba… 3 1 1 4a8ccc4c8ae3d658… 3 1 1 7acc5ebfd159a58b…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