Hostname
amadossf.com
Last fetched
amadossf.com resolves to 12 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in HU. WHOIS lists iana:146 as the registrar.
Nutrition Label
Resolution chain
amadossf.com resolves to 12 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 18.172.242.125 | 18.172.240.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | HU |
| 18.172.242.127 | 18.172.240.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | HU |
| 18.172.242.70 | 18.172.240.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | HU |
| 18.172.242.95 | 18.172.240.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | HU |
| 3.165.113.100 | 3.165.112.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | FR |
| 3.165.113.107 | 3.165.112.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | FR |
| 3.165.113.58 | 3.165.112.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | FR |
| 3.165.113.78 | 3.165.112.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | FR |
| 3.173.238.103 | 3.173.236.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | JP |
| 3.173.238.56 | 3.173.236.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | JP |
| 3.173.238.82 | 3.173.236.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | JP |
| 3.173.238.88 | 3.173.236.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | JP |
WHOIS identity
- Registrar
- iana:146
- Organization
- david quinby
- Contact emails
Subdomains
2 observed subdomains of amadossf.com.
| Subdomain |
|---|
| api.amadossf.com |
| www.amadossf.com |
Web-graph footprint
Distinct hostnames that link to or from amadossf.com in the public web crawl.
20 sites link to this hostname.
5 sites linked to from this hostname.
Sample inbound links
Sample outbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
1 SPF mechanism authorising senders for amadossf.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | _spf.google.com |
Related pages
Pivot deeper into the graph from amadossf.com.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "amadossf.com"})-[: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.