SurfaceMap › r › regfox.com

regfox.com

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

Domain & DNS

warn

26 passed 2 warn 0 failed

Areas

iRegistration iDelegation ✓Nameservers ✓SOA !DNSSEC !Records

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
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), AAAA (1m). Low TTLs are useful just before a planned change.
    #32

Recent checks

!

Full report

Domain & DNS report for regfox.com ›

Mail

warn

27 passed 5 warn 0 failed

Areas

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

Problems

  • !
    Policy: quarantine
    DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: google (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    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: *.mail.us-west-2.awsapps.com): aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com, alt4.aspmx.l.google.com. This will break delivery once the policy is enforced.
    #34

Recent checks

!

Full report

Mail report for regfox.com ›