SurfaceMap › r › royalmint.com

royalmint.com

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

Domain & DNS

warn

27 passed 1 warn 0 failed

Areas

iRegistration iDelegation iNameservers !SOA iDNSSEC iRecords

Problems

  • !
    Unusual SOA timers
    SOA · refresh 16m40s is outside 20m–1d. Current values: refresh 16m40s, retry 10m, expire 7d, negative TTL 5m.
    #23

Recent checks

!

Full report

Domain & DNS report for royalmint.com ›

Mail

warn

25 passed 6 warn 0 failed

Areas

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

Problems

  • !
    Hosts without IP addresses
    MX · The following MX hosts could not be resolved to IP addresses: 886.royalmint.com.royalmint.com
    #10
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: 886.royalmint.com.royalmint.com, uk.mx1.mailanyone.net, uk.mx2.mx25.net, uk.mx3.mailanyone.net, uk.mx4.mx25.net
    #11
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits), selector1 (1024 bits), selector2 (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
  • !
    Not configured
    TLS · MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".
    #35
  • !
    Not all MX hosts use DANE
    TLS · These MX hosts publish no TLSA records, so mail to them is not protected by DANE: 886.royalmint.com.royalmint.com.
    #36

Recent checks

!

Full report

Mail report for royalmint.com ›