Hostname
nasher.io
Last fetched
nasher.io resolves to 16 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in BR. WHOIS lists iana:1068 as the registrar.
Nutrition Label
Resolution chain
nasher.io resolves to 16 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 16.12.2.59 | 16.12.2.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | BR |
| 3.5.232.231 | 3.5.232.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | BR |
| 3.5.232.239 | 3.5.232.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | BR |
| 3.5.232.38 | 3.5.232.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | BR |
| 3.5.232.53 | 3.5.232.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | BR |
| 3.5.233.10 | 3.5.233.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | BR |
| 3.5.233.17 | 3.5.233.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | BR |
| 3.5.233.31 | 3.5.233.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | BR |
| 3.5.233.39 | 3.5.233.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | BR |
| 3.5.234.215 | 3.5.234.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | BR |
| 3.5.234.224 | 3.5.234.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | BR |
| 3.5.234.241 | 3.5.234.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | BR |
| 3.5.234.251 | 3.5.234.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | BR |
| 52.95.163.42 | 52.95.163.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | BR |
| 52.95.163.91 | 52.95.163.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | BR |
| 52.95.164.1 | 52.95.164.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | BR |
WHOIS identity
- Registrar
- iana:1068
- Organization
- privacy service provided by withheld for privacy ehf
- Contact emails
- —
Subdomains
27 observed subdomains of nasher.io.
Threat posture
History
Mail and authentication
MX records
SPF policy
3 SPF mechanisms authorising senders for nasher.io.
| Mechanism | Target |
|---|---|
| SPF_A | nasher.io |
| SPF_IP | 186.209.113.101 |
| SPF_MX | nasher.io |
Related pages
Pivot deeper into the graph from nasher.io.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "nasher.io"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.