Hostname
neurodynamo.com
Last fetched
neurodynamo.com resolves to 18.155.1.105, announced in 18.155.1.0/24 by AMAZON-02 - Amazon.com, Inc. in US. neurodynamo.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.155.1.105
18.155.1.0/24 · AMAZON-02 - Amazon.com, Inc. · Atlanta, US
- 18.155.1.24
18.155.1.0/24 · AMAZON-02 - Amazon.com, Inc. · Atlanta, US
- 18.155.1.67
18.155.1.0/24 · AMAZON-02 - Amazon.com, Inc. · Atlanta, US
- 18.155.1.74
18.155.1.0/24 · AMAZON-02 - Amazon.com, Inc. · Atlanta, US
- 54.192.151.118
54.192.151.0/24 · AMAZON-02 - Amazon.com, Inc. · Kolkata, IN
- 54.192.151.122
54.192.151.0/24 · AMAZON-02 - Amazon.com, Inc. · Kolkata, IN
- 54.192.151.51
54.192.151.0/24 · AMAZON-02 - Amazon.com, Inc. · Kolkata, IN
- 54.192.151.65
54.192.151.0/24 · AMAZON-02 - Amazon.com, Inc. · Kolkata, IN
IPv6 resolution
No AAAA record for neurodynamo.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- on behalf of neurodynamo.com owner
- Contact emails
- david.wallace.croft@gmail.com, 58ad29fe-c257-472d-b83c-7739c4ed69f0@identity-protect.org, 86a01116-5429-4031-83f5-c12d44b1f5a6@identity-protect.org
Subdomains
| Subdomain |
|---|
| www.neurodynamo.com |
Showing 1 of 1 subdomain (1 per page).
Mail and authentication
Nameservers
- ns-371.awsdns-46.com
- ns-934.awsdns-52.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-1056.awsdns-04.org
- ns-1808.awsdns-34.co.uk
Threat-feed evidence
History
Related pages
Pivot from neurodynamo.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: "neurodynamo.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.