aida.de

Checked 21 October 2026, 21:28 UTC · via 8.8.8.8
!Passed with warnings
26 passed 5 warnings 0 failed 2 info

SPF

pass

SPF record published

Found

Record
v=spf1 mx include:spf.protection.outlook.com a:smtpw.cytric.net include:inxserver.com ip4:141.144.229.35 ip4:138.2.142.134 ip4:54.171.131.249 include:spf.tds.de mx:costa.it ip4:185.18.100.0/24 include:amazonses.com ip4:213.146.75.21 ip4:213.146.75.22 ip4:213.146.75.23 -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

warn

p=quarantine (_dmarc.aida.de)

Found

Record
v=DMARC1; p=quarantine; rua=mailto:ij1phltz@dmarc.inxmail.de,mailto:carnivaldmarc@aida.de;
Found at
_dmarc.aida.de
External report address
mailto:ij1phltz@dmarc.inxmail.de (authorized)
TagValueMeaning
vDMARC1Version
pquarantinePolicy
ruamailto:ij1phltz@dmarc.inxmail.de,mailto:carnivaldmarc@aida.deAggregate report addresses

Checks

  • !
    Policy: quarantine
    DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Applies to 100% of mail #18
    DMARC policy applies to all failing mail.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:ij1phltz@dmarc.inxmail.de, mailto:carnivaldmarc@aida.de
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: selector1, selector2, s1, s2

Found

Selectors
selector1, selector2, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
selector1RSA 2048 bits
selector2RSA 2048 bits
s1RSA 2048 bits
s2RSA 1024 bits

Checks

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

1 mail server

Found

PriorityHostRecordsReverse DNS
5aida-de.mail.protection.outlook.comA 52.101.194.13 A 52.101.40.28 A 52.101.202.150 A 52.101.41.28 AAAA 2a01:111:f403:f903::3 AAAA 2a01:111:f403:c902:: AAAA 2a01:111:f403:f904::2 AAAA 2a01:111:f403:c927::8mail-ch0pr04cu00605.inbound.protection.outlook.com ✓ mail-cy1pr02cu00104.inbound.protection.outlook.com ✓ mail-ph6pr04cu00106.inbound.protection.outlook.com ✓ mail-sj0pr03cu01504.inbound.protection.outlook.com ✓ mail-mn0pr04cu00203.inbound.protection.outlook.com ✓ mail-sj2pr05cu00300.inbound.protection.outlook.com ✓ mail-ds2pr05cu00102.inbound.protection.outlook.com ✓ mail-bn3pr0301cu00200.inbound.protection.outlook.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.
  • ✓ All hosts have IPv6 #11
    All MX records resolve to IPv6 addresses.
  • !
    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 8 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
aida-de.mail.protection.outlook.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

pass

https://s3.eu-west-1.amazonaws.com/de.aida.bimi/aida_cruises.svg

Found

Record
v=BIMI1;l=https://s3.eu-west-1.amazonaws.com/de.aida.bimi/aida_cruises.svg;a=https://s3.eu-west-1.amazonaws.com/de.aida.bimi/aida_cruises.pem;
Found at
default._bimi.aida.de
Logo
https://s3.eu-west-1.amazonaws.com/de.aida.bimi/aida_cruises.svg
Certificate
https://s3.eu-west-1.amazonaws.com/de.aida.bimi/aida_cruises.pem

Checks

  • ✓ Logo and certificate published #38
    BIMI logo: https://s3.eu-west-1.amazonaws.com/de.aida.bimi/aida_cruises.svg; certificate: https://s3.eu-west-1.amazonaws.com/de.aida.bimi/aida_cruises.pem
  • ✓ DMARC meets BIMI requirements #39
    DMARC is enforced on all mail, as BIMI requires.