SurfaceMap › r › rsmus.com

rsmus.com

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

Domain & DNS

fail

20 passed 4 warn 2 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): fwd02dmzadc01.rsm02dmz.net, fwd02dmzadc02.rsm02dmz.net, fwd02dmzdns03.rsm02dmz.net, fwd02dmzdns04.rsm02dmz.net.
    #9
  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: fwddmzadc01.rsmdmz.net (66.98.100.40): read udp 46.225.38.91:51204->66.98.100.40:53: i/o timeout; fwddmzadc01.rsmdmz.net (66.98.100.23): read udp 46.225.38.91:41589->66.98.100.23:53: i/o timeout; fwddmzadc01.rsmdmz.net (66.98.100.123): read udp 46.225.38.91:52393->66.98.100.123:53: i/o timeout; fwddmzadc01.rsmdmz.net (66.98.100.43): read udp 46.225.38.91:38241->66.98.100.43:53: i/o timeout; fwddmzadc02.rsmdmz.net (66.98.100.24): read udp 46.225.38.91:53237->66.98.100.24:53: i/o timeout; fwddmzadc02.rsmdmz.net (66.98.100.124): read udp 46.225.38.91:37244->66.98.100.124:53: i/o timeout; fwddmzadc02.rsmdmz.net (66.98.100.41): read udp 46.225.38.91:50219->66.98.100.41:53: i/o timeout; fwddmzadc02.rsmdmz.net (66.98.100.44): read udp 46.225.38.91:52883->66.98.100.44:53: i/o timeout; fwddmzadc03.rsmdmz.net (66.98.100.23): read udp 46.225.38.91:47681->66.98.100.23:53: i/o timeout; fwddmzadc03.rsmdmz.net (2002:4262:6417::4262:6417): read udp [2a01:4f8:1c1c:eebf::1]:43088->[2002:4262:6417::4262:6417]:53: i/o timeout; fwddmzadc04.rsmdmz.net (2002:4262:6418::4262:6418): read udp [2a01:4f8:1c1c:eebf::1]:49983->[2002:4262:6418::4262:6418]:53: i/o timeout.
    #14
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: fwd02dmzadc01.rsm02dmz.net, fwd02dmzadc02.rsm02dmz.net, fwd02dmzdns03.rsm02dmz.net, fwd02dmzdns04.rsm02dmz.net, fwddmzadc01.rsmdmz.net, fwddmzadc02.rsmdmz.net, fwddmzadc03.rsmdmz.net, fwddmzadc04.rsmdmz.net. ns1.mcgladrey.com report NS fwd02dmzdns02.rsm02dmz.net fwddmzadc01.rsmdmz.net fwddmzadc02.rsmdmz.net fwddmzadc03.rsmdmz.net fwddmzadc04.rsmdmz.net fwddmzdns01.rsmdmz.net fwddmzdns02.rsmdmz.net fwddmzdns03.rsmdmz.net fwddmzdns04.rsmdmz.net ns1.mcgladrey.com ns2.mcgladrey.com. ns2.mcgladrey.com report NS fwd02dmzadc01.rsm02dmz.net fwd02dmzadc02.rsm02dmz.net fwd02dmzdns03.rsm02dmz.net fwd02dmzdns04.rsm02dmz.net fwddmzadc01.rsmdmz.net fwddmzadc02.rsmdmz.net fwddmzadc03.rsmdmz.net fwddmzadc04.rsmdmz.net ns1.mcgladrey.com ns2.mcgladrey.com.
    #7
  • !
    Serials differ
    SOA · The nameservers serve different versions of the zone: 3982 on ns2.mcgladrey.com (66.98.108.59); 4149 on ns1.mcgladrey.com (66.98.100.58). 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 · refresh 15m is outside 20m–1d; expire 1d is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 15m, retry 10m, expire 1d, negative TTL 1h.
    #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 rsmus.com ›

Mail

fail

22 passed 4 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
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: k1 (1024 bits), selector2 (1024 bits), s2 (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 rsmus.com ›