dogado.de

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

SPF

fail

SPF record published

Found

Record
v=spf1 include:_spf.cio.g1i.one include:spf.protection.outlook.com include:secure-mailgate.com include:eu.zcsend.net include:user.zohobookings.eu ip4:195.34.83.113 ip4:31.47.251.1 ip4:192.162.84.138 ip4:195.34.83.144 include:mail.zendesk.com include:spf.mx-out01.mhc.dogado.net ip4:137.74.38.167 include:mailgun.org ~all
DNS lookups
17 of 10
Void lookups
1 of 2
Problem
include:spf.mx-out.mhc does not exist or has no records

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✗
    17 DNS lookups, over the limit of 10
    SPF record needs 17 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record. Problems found: include:spf.mx-out.mhc does not exist or has no records.
    #2
  • ✓ 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.
  • !
    1 void lookup
    1 include/redirect target does not exist or has no records (limit is 2). This usually is a stale include; remove it.
    #26
  • ✓ No overly broad IP ranges #27
    All ip4/ip6 ranges are narrow enough.

DMARC

fail

p=none (_dmarc.dogado.de)

Found

Record
v=DMARC1;p=none;sp=none;pct=100;aspf=s;rua=mailto:dmarc@cp.wum.dogado.net,mailto:noreply-dmarc@dogado.de;ruf=mailto:dmarc@cp.wum.dogado.net,mailto:noreply-dmarc@dogado.de;ri=86400;fo=s
Found at
_dmarc.dogado.de
External report address
mailto:dmarc@cp.wum.dogado.net (authorized)
TagValueMeaning
vDMARC1Version
pnonePolicy
spnoneSubdomain policy
pct100Percentage of mail the policy applies to
ruamailto:dmarc@cp.wum.dogado.net,mailto:noreply-dmarc@dogado.deAggregate report addresses
rufmailto:dmarc@cp.wum.dogado.net,mailto:noreply-dmarc@dogado.deFailure report addresses
aspfsSPF alignment (r = relaxed, s = strict)
fosFailure reporting options
ri86400Report interval (seconds)

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@cp.wum.dogado.net, mailto:noreply-dmarc@dogado.de
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: mail, selector1, selector2, s1

Found

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

Checks

  • ✓ Keys found: mail, selector1, selector2, s1 #7
    DKIM keys found for this domain with selectors: mail, selector1, selector2, s1
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits), selector1 (1024 bits), s1 (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

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
10mx03.secure-mailgate.comA 46.243.95.104 A 46.243.95.105minc01.secure-mailgate.com ✓ minc02.secure-mailgate.com ✓
10mx04.secure-mailgate.comA 46.243.95.107 A 46.243.95.106minc04.secure-mailgate.com ✓ minc03.secure-mailgate.com ✓

Checks

  • ✓ 2 MX records #9
    Found 2 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: mx03.secure-mailgate.com, mx04.secure-mailgate.com
    #11
  • ✓ 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.
  • ✓ Reverse DNS confirmed #30
    All 4 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx03.secure-mailgate.comnone-
mx04.secure-mailgate.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