SurfaceMap › o › ours.com

ours.com

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

Domain & DNS

fail

20 passed 4 warn 1 failed

Areas

iRegistration ✗Delegation !Nameservers ✓SOA !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): ns1.50-6-174-130.www.hostgator.com, ns2.50-6-174-130.www.hostgator.com.
    #9
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns1.a20.com, ns2.a20.com; only in the zone: ns1.50-6-174-130.www.hostgator.com, ns2.50-6-174-130.www.hostgator.com. ns1.a20.com, ns2.a20.com report NS ns1.50-6-174-130.www.hostgator.com ns2.50-6-174-130.www.hostgator.com.
    #7
  • !
    Nameservers in one network
    Delegation · all IPv4 addresses are in 50.6.174.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.a20.com: "PowerDNS Authoritative Server 5.1.4 (built Aug 10 2026 00:00:00 by root@bh-centos-9.dev.cpanel.net)"; ns2.a20.com: "PowerDNS Authoritative Server 5.1.4 (built Aug 10 2026 00:00:00 by root@bh-centos-9.dev.cpanel.net)". Hide or replace the version string.
    #17
  • !
    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 ours.com ›

Mail

warn

24 passed 5 warn 0 failed

Areas

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

Problems

  • !
    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: mail.ours.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
  • !
    Hosts are CNAMEs
    MX · MX records must point to a host name with A/AAAA records, not to a CNAME: mail.ours.com -> ours.com
    #22
  • !
    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 ours.com ›