SurfaceMap › s › sick.com

sick.com

Checked 2026-10-22 10:42 UTC · first added 2026-10-21
✗Problems found Score 62 of 100

Domain & DNS

fail

24 passed 1 warn 2 failed

Areas

iRegistration iDelegation ✗Nameservers ✓SOA !DNSSEC iRecords

Problems

  • ✗
    Lame delegation
    Nameservers · These nameservers don't answer authoritatively for the zone, so resolvers ignore them: pns.dtag.de (194.25.0.125): SERVFAIL, authoritative=false; pns.dtag.de (2003:40:8000::100): SERVFAIL, authoritative=false; secondary004.dtag.net (195.244.245.27): SERVFAIL, authoritative=false; secondary004.dtag.net (2a00:fa8:3:0:100:0:4:1): SERVFAIL, authoritative=false.
    #15
  • ✗
    No DNS over TCP
    Nameservers · DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns.sick.de (91.207.92.80): dial tcp 91.207.92.80:53: i/o timeout; pns.dtag.de (194.25.0.125): ; pns.dtag.de (2003:40:8000::100): ; secondary004.dtag.net (195.244.245.27): ; secondary004.dtag.net (2a00:fa8:3:0:100:0:4:1): .
    #19
  • !
    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 sick.com ›

Mail

warn

22 passed 5 warn 0 failed

Areas

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

Problems

  • !
    Policy: quarantine
    DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • !
    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: mxa-001e4f01.gslb.pphosted.com, mxb-001e4f01.gslb.pphosted.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 sick.com ›