Hostname
215th.com
Last fetched
215th.com resolves to 108.156.224.113, announced in 108.156.224.0/21 by AMAZON-02 - Amazon.com, Inc. in US. 215th.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
- 108.156.224.113
108.156.224.0/21 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 108.156.224.44
108.156.224.0/21 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 108.156.224.61
108.156.224.0/21 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 108.156.224.63
108.156.224.0/21 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 3.171.139.104
3.171.136.0/22 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 3.171.139.109
3.171.136.0/22 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 3.171.139.110
3.171.136.0/22 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 3.171.139.98
3.171.136.0/22 · AMAZON-02 - Amazon.com, Inc. · New York, US
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- on behalf of 215th.com owner
- Contact emails
- 215th.com@protecteddomainservices.com, b2bdaf5d-804a-4315-a856-2d1b1ec031e3@identity-protect.org, d941ee76-7a1c-4327-8ffc-1e43345fddcd@identity-protect.org, owner-5565245@215th.com.whoisprivacyservice.org
Mail and authentication
Nameservers
- ns-48.awsdns-06.com
- ns-953.awsdns-55.net
- 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
- ns-1318.awsdns-36.org
- ns-1677.awsdns-17.co.uk
MX records
- in1-smtp.messagingengine.com
- in2-smtp.messagingengine.com
SPF policy
- include: spf.messagingengine.com
Threat-feed evidence
History
Related pages
Pivot from 215th.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: "215th.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.