Hostname
nanomedbase.com
Last fetched
nanomedbase.com resolves to 108.138.106.104, announced in 108.138.106.0/23 by AMAZON-02 - Amazon.com, Inc. in US. nanomedbase.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.138.106.104
108.138.106.0/23 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 108.138.106.127
108.138.106.0/23 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 108.138.106.52
108.138.106.0/23 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 108.138.106.58
108.138.106.0/23 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 18.165.140.41
18.165.136.0/21 · AMAZON-02 - Amazon.com, Inc. · Helsinki, FI
- 18.165.140.50
18.165.136.0/21 · AMAZON-02 - Amazon.com, Inc. · Helsinki, FI
- 18.165.140.55
18.165.136.0/21 · AMAZON-02 - Amazon.com, Inc. · Helsinki, FI
- 18.165.140.76
18.165.136.0/21 · AMAZON-02 - Amazon.com, Inc. · Helsinki, FI
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- on behalf of nanomedbase.com owner
- Contact emails
- 11f35fdc-99f4-44c7-8f23-07ed67053983@identity-protect.org, 217c037e-b1bf-43d4-934c-4d82dd02c7cd@identity-protect.org, 2d34e9da-ef80-471f-ab18-9af756d6199f@identity-protect.org, 32eaae2e-e04f-4af8-aefe-0e2472433ea1@identity-protect.org, 38ecd454-4f14-4196-ae1c-51665223ecf5@identity-protect.org, 72dd2957-2e65-49e4-8a67-4464f3440fad@identity-protect.org, cf069abf-0cbe-483e-861d-92b348b88bdf@identity-protect.org, owner-5543585@nanomedbase.com.whoisprivacyservice.org
Subdomains
Showing 2 of 2 subdomains (2 per page).
Mail and authentication
Nameservers
- ns-44.awsdns-05.com
- ns-720.awsdns-26.net
- ns-1246.awsdns-27.org
- ns-1965.awsdns-53.co.uk
Threat-feed evidence
History
Related pages
Pivot from nanomedbase.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: "nanomedbase.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.