Hostname
api.usemonocle.com
Last fetched
api.usemonocle.com resolves to 18.204.192.18, announced in 18.204.0.0/14 by AMAZON-AES - Amazon.com, Inc. in US. api.usemonocle.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.192.18
18.204.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.211.213.249
3.208.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.217.142.200
3.208.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.222.22.39
3.208.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 34.194.151.138
34.192.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 35.169.217.172
35.168.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 35.173.104.21
35.168.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 44.223.250.11
44.192.0.0/11 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.20.151.112
52.20.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.44.0.173
52.44.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.83.65.251
54.80.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 98.80.31.56
98.80.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 32.193.199.41
32.192.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
IPv6 resolution
No AAAA record for api.usemonocle.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for api.usemonocle.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.
Mail and authentication
Nameservers
- ns-59.awsdns-07.com
- ns-1011.awsdns-62.net
- ns-1219.awsdns-24.org
- ns-1846.awsdns-38.co.uk
Threat-feed evidence
History
Related pages
Pivot from api.usemonocle.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: "api.usemonocle.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.