Hostname
easyms.com
Last fetched
easyms.com resolves to 13.134.187.12, announced in 13.134.0.0/15 by AMAZON-02 - Amazon.com, Inc. in GB. easyms.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
- 13.134.187.12
13.134.0.0/15 · AMAZON-02 - Amazon.com, Inc. · London, GB
- 13.135.160.41
13.134.0.0/15 · AMAZON-02 - Amazon.com, Inc. · London, GB
- 13.135.48.204
13.134.0.0/15 · AMAZON-02 - Amazon.com, Inc. · London, GB
- 13.41.167.159
13.40.0.0/14 · AMAZON-02 - Amazon.com, Inc. · London, GB
- 13.41.232.146
13.40.0.0/14 · AMAZON-02 - Amazon.com, Inc. · London, GB
- 13.42.93.57
- 18.170.187.124
18.168.0.0/14 · AMAZON-02 - Amazon.com, Inc. · London, GB
- 3.10.84.136
3.8.0.0/14 · AMAZON-02 - Amazon.com, Inc. · London, GB
- 3.11.218.104
3.8.0.0/14 · AMAZON-02 - Amazon.com, Inc. · London, GB
- 3.9.210.38
3.8.0.0/14 · AMAZON-02 - Amazon.com, Inc. · London, GB
- 35.177.65.6
35.176.0.0/15 · AMAZON-02 - Amazon.com, Inc. · London, GB
- 52.56.33.96
52.56.0.0/16 · AMAZON-02 - Amazon.com, Inc. · London, GB
- 16.60.203.175
16.60.128.0/17 · AMAZON-02 - Amazon.com, Inc. · London, GB
- 16.61.3.162
16.61.0.0/17 · AMAZON-02 - Amazon.com, Inc. · London, GB
- 16.60.145.217
16.60.128.0/17 · AMAZON-02 - Amazon.com, Inc. · London, GB
- 13.135.228.159
13.134.0.0/15 · AMAZON-02 - Amazon.com, Inc. · London, GB
- 13.135.225.23
IPv6 resolution
No AAAA record for easyms.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:146
- Registrant organisation
- domains by proxy,
- Contact emails
- easyms.com@domainsbyproxy.com
Subdomains
Showing 4 of 4 subdomains (4 per page).
Mail and authentication
Nameservers
- ns-295.awsdns-36.com
- ns-926.awsdns-51.net
- ns-1404.awsdns-47.org
- ns-1562.awsdns-03.co.uk
Threat-feed evidence
History
Related pages
Pivot from easyms.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: "easyms.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.