SurfaceMap › w › wn.com

wn.com

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

Domain & DNS

fail

18 passed 5 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers !SOA !DNSSEC iRecords

Problems

  • ✗
    Zone transfer allowed
    Nameservers · These nameservers send the complete zone to anyone who asks (AXFR), exposing all host names: redbusprimarydns.wn.com (195.149.84.231): 1806 records; redbusprimarydns.wn.com (2001:67c:38c::e7): 1806 records; redbussecondarydns.wn.com (195.149.84.232): 1806 records; redbussecondarydns.wn.com (2001:67c:38c::e8): 1806 records. Restrict zone transfers to your secondary servers.
    #18
  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: redbusprimarydns.wn.com (glue 195.149.84.231, zone 195.149.84.231, 2001:67c:38c::e7); redbussecondarydns.wn.com (glue 195.149.84.232, zone 195.149.84.232, 2001:67c:38c::e8). Update the glue at your registrar.
    #8
  • !
    Nameservers in one network
    Delegation · all IPv4 addresses are in 195.149.84.0/24; all IPv6 addresses are in 2001:67c:38c::/48. 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: redbusprimarydns.wn.com: "9.18.49-1~deb12u2-Debian"; redbussecondarydns.wn.com: "9.18.49-1~deb12u2-Debian". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · refresh 2d is outside 20m–1d; negative caching TTL (minimum) 3m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 2d, retry 20m, expire 90d, negative TTL 3m.
    #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 wn.com ›

Mail

fail

20 passed 5 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
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    More than 5 MX records
    MX · Found 7 MX records, which is more than the recommended maximum of 5. Too many MX records may indicate a misconfiguration.
    #13
  • !
    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
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: k1 (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    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 wn.com ›