hochschule-trier.de

Checked 21 October 2026, 22:50 UTC · via 8.8.8.8
✗Problems found
26 passed 2 warnings 2 failed 2 info

SPF

info

SPF record published

Found

Record
v=spf1 redirect=_spf.hochschule-trier.de
DNS lookups
7 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 7 of 10 DNS lookups #2
    SPF record needs 7 DNS lookups (limit is 10).
  • i
    Delegated via redirect
    SPF record has no 'all' mechanism but redirects to _spf.hochschule-trier.de, whose policy applies.
    #3
  • ✓ 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.hochschule-trier.de)

Found

Record
v=DMARC1;p=none;pct=100;rua=mailto:dmarc-rua@hochschule-trier.de;ruf=mailto:dmarc-ruf@hochschule-trier.de;adkim=r;aspf=r
Found at
_dmarc.hochschule-trier.de
TagValueMeaning
vDMARC1Version
pnonePolicy
pct100Percentage of mail the policy applies to
ruamailto:dmarc-rua@hochschule-trier.deAggregate report addresses
rufmailto:dmarc-ruf@hochschule-trier.deFailure report addresses
adkimrDKIM alignment (r = relaxed, s = strict)
aspfrSPF alignment (r = relaxed, s = strict)

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-rua@hochschule-trier.de
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

warn

Selectors: default

Found

Selectors
default
_domainkey
NOERROR
SelectorKeyFlags
defaultRSA 1024 bits

Checks

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

pass

Signed, DS published at parent

Found

DNSKEY records
Yes (2)
DS at parent
Yes
Algorithms
RSASHA256 (8)
Key tags
45381, 36562
Signatures valid until
29 October 2026, 08:40 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-10-29 #21
    DNSKEY signatures are valid until 2026-10-29T08:40:09Z.

MX

warn

2 mail servers

Found

PriorityHostRecordsReverse DNS
10gateway-a.fh-trier.deA 143.93.54.181gateway-a.fh-trier.de ✓
10gateway-b.fh-trier.deA 143.93.54.182gateway-b.fh-trier.de ✓

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: gateway-a.fh-trier.de, gateway-b.fh-trier.de
    #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 2 MX addresss have a PTR record that resolves back to them.

TLS

fail

MTA-STS record without policy · TLS-RPT · DANE on 2 of 2 MX hosts

Found

MTA-STS record
v=STSv1; id=20260314223000
Policy URL
https://mta-sts.hochschule-trier.de/.well-known/mta-sts.txt
Policy error
Get "https://mta-sts.hochschule-trier.de/.well-known/mta-sts.txt": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
TLS-RPT record
v=TLSRPTv1; rua=mailto:tlsrpt-rua@hochschule-trier.de

DANE (TLSA records)

MX hostTLSADNSSEC
gateway-a.fh-trier.de3 1 2 6a64ac6beec18153… 3 1 1 960a64dff003562a… 3 1 1 5df2ed996009914e… 3 1 2 ab4f9074c5380207…Yes
gateway-b.fh-trier.de3 1 1 5df2ed996009914e… 3 1 2 ab4f9074c5380207… 3 1 1 960a64dff003562a… 3 1 2 6a64ac6beec18153…Yes

Checks

  • ✓ Record published #32
    MTA-STS record found with id 20260314223000.
  • ✗
    Policy not reachable
    The MTA-STS record exists but the policy could not be fetched, so senders ignore MTA-STS: Get "https://mta-sts.hochschule-trier.de/.well-known/mta-sts.txt": context deadline exceeded (Client.Timeout exceeded while awaiting headers).
    #33
  • ✓ Reports enabled #35
    TLS reports are sent to: mailto:tlsrpt-rua@hochschule-trier.de
  • ✓ DANE on all MX hosts #36
    All 2 MX hosts 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