SurfaceMap › i › informatechtarget.com

informatechtarget.com

Checked 2026-10-22 09:20 UTC · first added 2026-10-21
!Passed with warnings Score 73 of 100

Domain & DNS

warn

20 passed 5 warn 0 failed

Areas

iRegistration !Delegation iNameservers !SOA !DNSSEC !Records

Problems

  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: ns10.techtarget.com (glue 2600:180a:1001::1, 96.45.80.1, zone 96.45.80.1); ns11.techtarget.com (glue 2600:180b:2001::1, 46.31.236.1, zone 46.31.236.1); ns12.techtarget.com (glue 2600:180c:3001::1, 43.247.170.1, zone 43.247.170.1); ns13.techtarget.com (glue 2600:180a:4001::1, 96.45.81.1, zone 96.45.81.1); ns14.techtarget.com (glue 2600:180b:5001::1, 46.31.237.1, zone 46.31.237.1); ns15.techtarget.com (glue 2600:180c:6001::1, 43.247.171.1, zone 43.247.171.1). Update the glue at your registrar.
    #8
  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    Unusual SOA timers
    SOA · negative caching TTL (minimum) 3m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 12h, retry 1h, expire 14d, negative TTL 3m.
    #23
  • !
    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: MX (4m58s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 1d; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for informatechtarget.com ›

Mail

warn

25 passed 4 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
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: us-smtp-inbound-1.mimecast.com, us-smtp-inbound-2.mimecast.com
    #11
  • !
    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 informatechtarget.com ›