SurfaceMap › w › webcom.com

webcom.com

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

Domain & DNS

fail

21 passed 4 warn 2 failed

Areas

iRegistration !Delegation ✗Nameservers ✓SOA !DNSSEC iRecords

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: dns1.registeredsite.com (162.214.41.47): read udp 46.225.38.91:42077->162.214.41.47: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: dns2.registeredsite.com (207.204.21.31): dial tcp 207.204.21.31:53: i/o timeout; dns3.registeredsite.com (207.204.21.31): dial tcp 207.204.21.31:53: i/o timeout.
    #19
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: dns1.registeredsite.com; only in the zone: dns3.registeredsite.com. dns2.registeredsite.com, dns3.registeredsite.com report NS dns2.registeredsite.com dns3.registeredsite.com.
    #7
  • !
    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: dns2.registeredsite.com (207.204.21.31), dns3.registeredsite.com (207.204.21.31).
    #20
  • !
    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 webcom.com ›

Mail

fail

0 passed 2 warn 3 failed

Areas

✗SPF ✗DMARC ✗DKIM !DNSSEC !MX 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.webcom.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
  • !
    No MX records
    MX · No MX records found. If this domain is used for email, add MX records to specify mail servers. If it never receives mail, publish a null MX ("MX 0 .").
    #9

Recent checks

✗

Full report

Mail report for webcom.com ›