SurfaceMap › i › iobit.com

iobit.com

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

Domain & DNS

warn

23 passed 2 warn 0 failed

Areas

iRegistration !Delegation ✓Nameservers ✓SOA !DNSSEC iRecords

Problems

  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: ns.liquidweb.com (glue 69.16.222.254, zone 69.16.222.254, 2607:fad0:0:8917::a); ns1.liquidweb.com (glue 69.16.223.254, zone 69.16.223.254, 2607:fad0:0:8927::a). Update the glue at your registrar.
    #8
  • !
    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 iobit.com ›

Mail

fail

19 passed 6 warn 1 failed

Areas

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

Problems

  • ✗
    No DKIM keys published
    DKIM · _domainkey.iobit.com does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • !
    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
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mx1.emailsrvr.com, mx2.emailsrvr.com
    #11
  • !
    No aggregate reports (rua)
    DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • !
    Reverse DNS does not match
    MX · The PTR name of these addresses does not resolve back to the same address: 173.203.187.1 -> mx1.emailsrvr.com, 184.106.54.1 -> mx1.emailsrvr.com, 146.20.161.1 -> mx1.emailsrvr.com, 108.166.43.1 -> mx1.emailsrvr.com, 184.106.54.2 -> mx2.emailsrvr.com.
    #30
  • !
    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 iobit.com ›