SurfaceMap › i › ivoox.com

ivoox.com

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

Domain & DNS

warn

25 passed 1 warn 0 failed

Areas

iRegistration iDelegation ✓Nameservers ✓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 ivoox.com ›

Mail

fail

22 passed 5 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
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: default (1024 bits), mail (1024 bits), google (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Key in test mode
    DKIM · These keys have t=y, so receivers treat DKIM failures as a test: default. Remove t=y once DKIM works.
    #24
  • !
    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 all MX hosts use DANE
    TLS · These MX hosts publish no TLSA records, so mail to them is not protected by DANE: aspmx.l.google.com, alt1.aspmx.l.google.com, aspmx2.googlemail.com, aspmx3.googlemail.com.
    #36

Recent checks

✗

Full report

Mail report for ivoox.com ›