Hostname
edge-proxy.inintca.com
Last fetched
edge-proxy.inintca.com resolves to 100.29.90.131, announced in 100.24.0.0/13 by AMAZON-AES - Amazon.com, Inc. in US. edge-proxy.inintca.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 100.29.90.131
100.24.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 18.214.109.0
18.208.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.211.173.41
3.208.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 35.169.150.171
35.168.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 44.208.242.221
44.192.0.0/11 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 44.215.4.4
44.192.0.0/11 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.55.76.203
52.54.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.236.125.99
54.236.64.0/18 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 98.88.95.147
98.88.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
IPv6 resolution
No AAAA record for edge-proxy.inintca.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for edge-proxy.inintca.com. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.
Subdomains
| Subdomain |
|---|
| public.edge-proxy.inintca.com |
Showing 1 of 1 subdomain (1 per page).
Mail and authentication
Nameservers
- 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
Threat-feed evidence
History
Related pages
Pivot from edge-proxy.inintca.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: "edge-proxy.inintca.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.