SurfaceMap › w › woerxny.com

woerxny.com

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

Domain & DNS

fail

19 passed 3 warn 1 failed

Areas

iRegistration iDelegation ✗Nameservers !SOA !DNSSEC iRecords

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: dns10.hichina.com (2408:4009:501::18): read udp [2a01:4f8:1c1c:eebf::1]:41881->[2408:4009:501::18]:53: i/o timeout.
    #14
  • !
    Serials differ
    SOA · The nameservers serve different versions of the zone: 2016101809 on dns10.hichina.com (139.224.142.111); 2026081813 on dns10.hichina.com (120.76.107.51); 2026082509 on dns10.hichina.com (120.76.107.41), dns9.hichina.com (120.76.107.52), dns9.hichina.com (120.76.107.42); 2026082616 on dns10.hichina.com (139.224.142.121), dns10.hichina.com (39.96.153.51), dns10.hichina.com (47.118.199.201), dns9.hichina.com (47.118.199.202), dns9.hichina.com (47.118.199.212), dns9.hichina.com (139.224.142.122), dns9.hichina.com (139.224.142.112), dns9.hichina.com (39.96.153.42); 2026082617 on dns10.hichina.com (47.118.199.211), dns10.hichina.com (39.96.153.41), dns9.hichina.com (39.96.153.52), dns9.hichina.com (2408:4009:501::17). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22
  • !
    Unusual SOA timers
    SOA · expire 1d is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 1h, retry 20m, expire 1d, 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

Recent checks

✗

Full report

Domain & DNS report for woerxny.com ›

Mail

fail

17 passed 7 warn 1 failed

Areas

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

Problems

  • ✗
    Policy: none (monitoring only)
    DMARC · DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • !
    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: mail.woerxny.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
  • !
    No aggregate reports (rua)
    DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 121.35.240.168 (mail.woerxny.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 woerxny.com ›