Hostname
ironmount.com
Last fetched
ironmount.com resolves to 18.204.122.93, announced in 18.204.0.0/14 by AMAZON-AES - Amazon.com, Inc. in US. ironmount.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
- 18.204.122.93
18.204.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.0.102.3
52.0.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.3.215.65
52.2.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.54.83.69
52.54.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.72.6.68
52.72.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.146.61.89
54.144.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.147.237.40
54.144.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.166.91.69
54.166.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.208.15.14
54.208.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.235.73.172
54.234.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 98.89.54.19
98.88.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 98.90.131.41
98.88.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
IPv6 resolution
No AAAA record for ironmount.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:146
- Registrant organisation
- domains by proxy,
- Contact emails
- ironmount.com@domainsbyproxy.com
Subdomains
Showing 3 of 3 subdomains (3 per page).
Mail and authentication
Nameservers
- ns-454.awsdns-56.com
- ns-518.awsdns-00.net
- ns-1141.awsdns-14.org
- ns-1558.awsdns-02.co.uk
MX records
- ironmount-com.mail.protection.outlook.com
SPF policy
- include: emailus.freshservice.com
- a: ironmount.com
- include: spf.protection.outlook.com
- ip: 174.77.153.26
- ip: 209.173.16.34
- ip: 210.61.72.8
- ip: 40.137.232.178
Threat-feed evidence
History
Related pages
Pivot from ironmount.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: "ironmount.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.