SurfaceMap › r › rocketnews24.com

rocketnews24.com

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

Domain & DNS

warn

24 passed 1 warn 0 failed

Areas

iRegistration iDelegation iNameservers ✓SOA !DNSSEC iRecords

Problems

  • !
    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 rocketnews24.com ›

Mail

warn

26 passed 6 warn 0 failed

Areas

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

Problems

  • !
    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), google (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@13hh3udk.uriports.com (needs rocketnews24.com._report._dmarc.13hh3udk.uriports.com). Ask the report provider to publish the record, or check the address.
    #29
  • !
    Policy in testing mode
    TLS · With mode: testing, senders only report TLS problems (via TLS-RPT) and still deliver without TLS. Switch to mode: enforce once reports are clean.
    #33
  • !
    MX hosts missing from policy
    TLS · These MX hosts are not listed in the MTA-STS policy (mx: alt3.aspmx.l.google.com, alt1.aspmx.l.google.com, aspmx.l.google.com, alt4.aspmx.l.google.com, alt2.aspmx.l.google.com): smtp.google.com. This will break delivery once the policy is enforced.
    #34

Recent checks

!

Full report

Mail report for rocketnews24.com ›