Hostname
lockated.com
Last fetched
lockated.com resolves to 13.232.88.94, announced in 13.232.0.0/14 by AMAZON-02 - Amazon.com, Inc. in IN. lockated.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.232.88.94
13.232.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 13.234.234.55
13.232.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 15.206.95.22
15.206.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 15.207.181.158
15.206.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 15.207.210.54
15.206.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 3.7.75.255
3.6.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 13.206.55.59
13.204.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 13.203.124.114
13.202.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 13.207.9.17
13.204.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 15.252.205.10
IPv6 resolution
No AAAA record for lockated.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:146
- Registrant organisation
- chetan bafna
- Contact emails
- chetanbafna@gmail.com
Subdomains
Mail and authentication
Nameservers
- ns-383.awsdns-47.com
- ns-543.awsdns-03.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-1169.awsdns-18.org
- ns-1946.awsdns-51.co.uk
MX records
- mail.lockated.com
SPF policy
- include: amazonses.com
- include: _spf.google.com
- ip: 13.200.173.33
- ip: 43.204.136.150
Threat-feed evidence
History
Related pages
Pivot from lockated.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: "lockated.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.