SurfaceMap › t › tmasgff.de

tmasgff.de

Checked 2026-10-22 00:41 UTC · first added 2026-10-21
✗Problems found Score 55 of 100

Domain & DNS

fail

22 passed 1 warn 1 failed

Areas

iRegistration iDelegation ✓Nameservers ✗SOA !DNSSEC iRecords

Problems

  • ✗
    Invalid contact address
    SOA · The SOA RNAME "hostmaster\\@alfahosting.de" contains an @; it must be written with a dot instead (hostmaster.example.com).
    #25
  • !
    Not signed
    DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Recent checks

✗

Full report

Domain & DNS report for tmasgff.de ›

Mail

fail

8 passed 4 warn 2 failed

Areas

✗SPF ✗DMARC !DKIM !DNSSEC !MX !TLS iBIMI

Problems

  • ✗
    No DMARC record
    DMARC · 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
  • ✗
    No SPF record
    SPF · No SPF record was found for this domain. SPF is important for preventing email spoofing. Add an SPF record to specify which servers are authorized to send email for your domain.
    #6
  • !
    No key under common selectors
    DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mx03.secure-mailgate.com, mx04.secure-mailgate.com
    #11
  • !
    Not configured
    TLS · 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

Recent checks

✗

Full report

Mail report for tmasgff.de ›