SurfaceMap › a › asuscomm.com

asuscomm.com

Checked 2026-10-22 07:50 UTC · first added 2026-10-21
✗Problems found Score 24 of 100

Domain & DNS

fail

18 passed 7 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers !SOA !DNSSEC !Records

Problems

  • ✗
    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-nw.asuscomm.com (52.250.42.40): dial tcp 52.250.42.40:53: connect: connection refused; ns2.asuscomm.com (52.250.42.40): dial tcp 52.250.42.40:53: connect: connection refused.
    #19
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns2.asuscomm.com. ns-nw.asuscomm.com, ns2.asuscomm.com report NS ns-nw.asuscomm.com.
    #7
  • !
    Nameservers in one network
    Delegation · all IPv4 addresses are in 52.250.42.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    No EDNS
    Nameservers · These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: ns-nw.asuscomm.com (52.250.42.40), ns2.asuscomm.com (52.250.42.40).
    #20
  • !
    Unusual SOA timers
    SOA · negative caching TTL (minimum) 30s is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 8h, retry 2h, expire 7d, negative TTL 30s.
    #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
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: MX (2m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 1d; resolvers may use either.
    #32

Recent checks

✗

Full report

Domain & DNS report for asuscomm.com ›

Mail

fail

5 passed 5 warn 3 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 DKIM keys published
    DKIM · _domainkey.asuscomm.com does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IP addresses
    MX · The following MX hosts could not be resolved to IP addresses: hostmaster.asuscomm.com
    #10
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: hostmaster.asuscomm.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 asuscomm.com ›