SurfaceMap › r › rd.com

rd.com

Checked 2026-10-22 10:25 UTC · first added 2026-10-21
!Passed with warnings Score 85 of 100

Domain & DNS

warn

28 passed 1 warn 0 failed

Areas

iRegistration iDelegation !Nameservers ✓SOA iDNSSEC iRecords

Problems

  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: jim.ns.cloudflare.com: "2026.10.2"; karina.ns.cloudflare.com: "2026.10.2". Hide or replace the version string.
    #17

Recent checks

!

Full report

Domain & DNS report for rd.com ›

Mail

warn

28 passed 4 warn 0 failed

Areas

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

Problems

  • !
    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: selector1 (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Report address not authorized
    DMARC · These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:dmarc-reports@bm16.maas.zetaglobal.net (needs rd.com._report._dmarc.bm16.maas.zetaglobal.net). Ask the report provider to publish the record, or check the address.
    #29
  • !
    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 rd.com ›