Skip to content

Hostname

validation-attackiq-ntm.com

Last fetched

validation-attackiq-ntm.com resolves to 13.226.244.26, announced in 13.226.244.0/22 by AMAZON-02 - Amazon.com, Inc. in DE. validation-attackiq-ntm.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · validation-attackiq-ntm.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/validation-attackiq-ntm.com

Resolution chain

IPv6 resolution

No AAAA record for validation-attackiq-ntm.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of validation-attackiq-ntm.com owner
Contact emails
03c3b892-acde-44cc-ae06-6f47b1b854c4@identity-protect.org, 4534d11f-81d2-4808-878c-d2c073052aff@identity-protect.org, 8441fac6-b6ef-42cf-afde-2021eb6c5b62@identity-protect.org, abe5484f-3b7b-4221-b2d8-9f40ed1b8670@identity-protect.org, ac3077df-8aee-427c-98ed-176c17a73d58@identity-protect.org, bb7ef999-1339-43e9-bb63-023d949e7ba0@identity-protect.org, d473ea53-f58a-4617-ba6c-2cbb2e465676@identity-protect.org, owner-8646766@validation-attackiq-ntm.com.whoisprivacyservice.org, owner-9561109@validation-attackiq-ntm.com.whoisprivacyservice.org

Mail and authentication

Nameservers

  • ns-54.awsdns-06.com
  • ns-853.awsdns-42.net
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net
  • ns-1205.awsdns-22.org
  • ns-1557.awsdns-02.co.uk

Threat-feed evidence

History

Related pages

Pivot from validation-attackiq-ntm.com into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "validation-attackiq-ntm.com"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.