SurfaceMap › s › sdo.com

sdo.com

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

Domain & DNS

warn

21 passed 5 warn 0 failed

Areas

iRegistration !Delegation !Nameservers !SOA !DNSSEC iRecords

Problems

  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns3.uugame.com. ns.uugame.com, ns1.uugame.com, ns2.uugame.com, ns3.uugame.com report NS ns.uugame.com ns1.uugame.com ns2.uugame.com.
    #7
  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns.uugame.com: "9.9.3-P2"; ns1.uugame.com: "9.9.3-P2"; ns2.uugame.com: "9.9.3-P2"; ns3.uugame.com: "9.9.3-P2". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · refresh 1m12s is outside 20m–1d; expire 1m12s is shorter than 7d; secondaries stop answering too soon when the primary is down; expire 1m12s must be longer than refresh + retry; negative caching TTL (minimum) 36s is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1m12s, retry 36s, expire 1m12s, negative TTL 36s.
    #23
  • !
    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 sdo.com ›

Mail

fail

13 passed 7 warn 1 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
  • !
    3 of 10 DNS lookups, with problems
    SPF · SPF record needs 3 DNS lookups (limit is 10). Problems found: include:artmail.sdo.com does not exist or has no records.
    #2
  • !
    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: mx1.sdo.com, mx2.sdo.com
    #11
  • !
    1 void lookup
    SPF · 1 include/redirect target does not exist or has no records (limit is 2). This usually is a stale include; remove it.
    #26
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 116.211.22.43 (mx1.sdo.com), 116.211.22.43 (mx2.sdo.com). Ask your hosting provider to set one.
    #30
  • !
    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 sdo.com ›