Skip to content

Hostname

innaitkey.com

Last fetched

innaitkey.com resolves to 52.66.50.36, announced in 52.66.32.0/19 by AMAZON-02 - Amazon.com, Inc. in IN. innaitkey.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 · innaitkey.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/innaitkey.com

Resolution chain

IPv6 resolution

No AAAA record for innaitkey.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of innaitkey.com owner
Contact emails
2d2d7ce0-b041-4543-87ff-d5e005eabdc3@identity-protect.org, 41890445-5356-4fca-8c6e-789c2332a9a2@identity-protect.org, 8a94af9f-c9b2-40d8-8c4f-fd5f8f893187@identity-protect.org, 91f4fc2c-3635-4417-a894-30758bd40b49@identity-protect.org, a065c6e1-ec9f-4924-985b-ee339fd9f3a0@identity-protect.org, ca596c4e-7fbf-4f4f-8fc7-58bc29150ca8@identity-protect.org, e8ed57f8-7a26-4d31-8e8c-53179297c573@identity-protect.org, owner-10523575@innaitkey.com.whoisprivacyservice.org

Subdomains

Subdomain
citrixgw.innaitkey.com
drivers.innaitkey.com
keygw.innaitkey.com
mail.innaitkey.com

Showing 4 of 4 subdomains (4 per page).

Mail and authentication

Nameservers

  • ns-353.awsdns-44.com
  • ns-981.awsdns-58.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-1288.awsdns-33.org
  • ns-1559.awsdns-02.co.uk

MX records

  • mail.innaitkey.com

Threat-feed evidence

History

Related pages

Pivot from innaitkey.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: "innaitkey.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.