SurfaceMap › h › hooyoo.com

hooyoo.com

Checked 2026-10-22 09:12 UTC · first added 2026-10-21
✗Problems found Score 17 of 100

Domain & DNS

fail

17 passed 6 warn 2 failed

Areas

iRegistration !Delegation ✗Nameservers !SOA !DNSSEC !Records

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: ns1.4everdns.com (61.240.129.114): read udp 46.225.38.91:46706->61.240.129.114:53: i/o timeout; ns1.4everdns.com (240c:4082:0:2503::4): read udp [2a01:4f8:1c1c:eebf::1]:50009->[240c:4082:0:2503::4]:53: i/o timeout; ns2.4everdns.com (240c:4082:0:2503::5): read udp [2a01:4f8:1c1c:eebf::1]:53934->[240c:4082:0:2503::5]:53: i/o timeout.
    #14
  • ✗
    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: ns1.4everdns.com (61.172.183.70): dial tcp 61.172.183.70:53: i/o timeout; ns2.4everdns.com (61.172.183.76): dial tcp 61.172.183.76:53: i/o timeout; ns2.4everdns.com (61.240.129.147): dial tcp 61.240.129.147:53: i/o timeout.
    #19
  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: ns1.4everdns.com (glue 180.163.194.139, 240c:4082:0:2503::4, 61.240.129.114, zone 61.240.129.114, 61.172.183.70, 240c:4082:0:2503::4); ns2.4everdns.com (glue 180.163.194.215, 240c:4082:0:2503::5, 61.240.129.147, zone 61.172.183.76, 61.240.129.147, 240c:4082:0:2503::5). Update the glue at your registrar.
    #8
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.4everdns.com: "9.11.0pre-alpha"; ns2.4everdns.com: "9.11.0pre-alpha". Hide or replace the version string.
    #17
  • !
    No EDNS
    Nameservers · These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: ns1.4everdns.com (61.172.183.70), ns2.4everdns.com (61.172.183.76).
    #20
  • !
    Unusual SOA timers
    SOA · expire 4h is shorter than 7d; secondaries stop answering too soon when the primary is down; expire 4h must be longer than refresh + retry. Current values: refresh 8h, retry 4h, expire 4h, negative TTL 10m.
    #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: A (2m), MX (2m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 10m; resolvers may use either.
    #32

Recent checks

✗

Full report

Domain & DNS report for hooyoo.com ›

Mail

fail

6 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.hooyoo.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 IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: s01mx.serverproof.net
    #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
  • !
    Reverse DNS does not match
    MX · The PTR name of these addresses does not resolve back to the same address: 139.9.119.183 -> ecs-139-9-119-183.compute.hwclouds-dns.com.
    #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 hooyoo.com ›