SurfaceMap › i › imageevent.com

imageevent.com

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

Domain & DNS

warn

22 passed 4 warn 0 failed

Areas

iRegistration !Delegation !Nameservers iSOA !DNSSEC ✓Records

Problems

  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: dns1.imageevent.com (glue 64.71.182.1, zone 64.71.182.1, 2001:470:4a2:1::1); dns2.imageevent.com (glue 64.71.182.2, zone 64.71.182.2, 2001:470:4a2:1::2); dns3.imageevent.com (glue 64.71.182.3, zone 64.71.182.3, 2001:470:4a2:1::3); dns4.imageevent.com (glue 64.71.182.4, zone 64.71.182.4, 2001:470:4a2:1::4). Update the glue at your registrar.
    #8
  • !
    Nameservers in one network
    Delegation · all IPv4 addresses are in 64.71.182.0/24; all IPv6 addresses are in 2001:470:4a2::/48. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: dns1.imageevent.com: "9.11.4-P2-RedHat-9.11.4-26.0.1.P2.el7_9.16"; dns1.imageevent.com: "9.11.36-RedHat-9.11.36-8.el8"; dns2.imageevent.com: "9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.7"; dns2.imageevent.com: "9.11.4-P2-RedHat-9.11.4-26.0.1.P2.el7_9.16"; dns3.imageevent.com: "9.11.36-RedHat-9.11.36-8.el8"; dns4.imageevent.com: "9.11.36-RedHat-9.11.36-8.el8"; dns4.imageevent.com: "9.11.4-P2-RedHat-9.11.4-26.0.1.P2.el7_9.16". Hide or replace the version string.
    #17
  • !
    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 imageevent.com ›

Mail

fail

21 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
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mail.imageevent.com
    #11
  • !
    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: default (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

Recent checks

✗

Full report

Mail report for imageevent.com ›