Hostname
cmfd.me
Last fetched
cmfd.me resolves to 100.25.131.238, announced in 100.24.0.0/13 by AMAZON-AES - Amazon.com, Inc. in US. cmfd.me 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.25.131.238
100.24.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 100.25.177.58
100.24.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 18.233.216.247
18.232.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.208.134.152
3.208.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 34.196.158.249
34.192.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 34.231.231.67
34.224.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 44.213.23.236
44.192.0.0/11 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 44.220.102.204
44.192.0.0/11 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 44.220.11.136
44.192.0.0/11 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 50.16.147.25
50.16.0.0/16 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.71.130.242
52.70.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.237.44.137
54.237.0.0/16 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.80.69.6
54.80.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.6.222.139
52.4.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 32.195.210.69
32.192.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 32.197.1.99
32.196.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.198.104.144
- 98.95.157.14
IPv6 resolution
No AAAA record for cmfd.me is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:146
- Registrant organisation
- domains by proxy,
Mail and authentication
Nameservers
- ns-160.awsdns-20.com
- ns-557.awsdns-05.net
- ns-1510.awsdns-60.org
- ns-1672.awsdns-17.co.uk
Threat-feed evidence
History
Related pages
Pivot from cmfd.me 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: "cmfd.me"})-[: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.