SurfaceMap › s › samsung.com

samsung.com

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

Domain & DNS

fail

20 passed 3 warn 2 failed

Areas

iRegistration ✗Delegation ✗Nameservers iSOA !DNSSEC iRecords

Problems

  • ✗
    Nameserver names don't resolve
    Delegation · These nameservers have no A or AAAA record, so they can't be reached (lame delegation): auth01.sam.ic.
    #9
  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: dns-gi2.samsung.com (203.241.135.186): read udp 46.225.38.91:48142->203.241.135.186:53: i/o timeout; dnssm2.samsung.com (2001:330:a:300b:112:107:53:58): read udp [2a01:4f8:1c1c:eebf::1]:41988->[2001:330:a:300b:112:107:53:58]:53: i/o timeout; dnsst2.samsung.com (2001:330:a:b:112:106:53:58): read udp [2a01:4f8:1c1c:eebf::1]:36252->[2001:330:a:b:112:106:53:58]:53: i/o timeout.
    #14
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: auth01.sam.ic, dns-gi2.samsung.com. dns-awskr1.samsung.com, dns-gi1.samsung.com, dns-gi2.samsung.com, dnssm.samsung.com, dnssm2.samsung.com, dnsst.samsung.com, dnsst2.samsung.com report NS auth01.sam.ic dns-awskr1.samsung.com dns-gi1.samsung.com dns-gi2.samsung.com dnssm.samsung.com dnssm2.samsung.com dnsst.samsung.com dnsst2.samsung.com.
    #7
  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: dnssm.samsung.com (glue 203.241.132.51, zone 203.241.132.51, 2001:330:a:300a:203:241:132:51); dnssm2.samsung.com (glue 112.107.53.58, zone 112.107.53.58, 2001:330:a:300b:112:107:53:58); dnsst.samsung.com (glue 203.241.135.51, zone 203.241.135.51, 2001:330:a:a:203:241:135:51); dnsst2.samsung.com (glue 112.106.53.58, zone 112.106.53.58, 2001:330:a:b:112:106:53:58). Update the glue at your registrar.
    #8
  • !
    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 samsung.com ›

Mail

fail

19 passed 5 warn 1 failed

Areas

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

Problems

  • ✗
    Policy: none (monitoring only)
    DMARC · DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #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: mailin.samsung.com
    #11
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    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 samsung.com ›