Hostname
argen.com
Last fetched
argen.com resolves to 13 IPv4 addresses operated by AMAZON-AES - Amazon.com, Inc. in US.
Nutrition Label
Resolution chain
argen.com resolves to 13 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 13.216.115.71 | 13.216.0.0/13 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 34.241.218.151 | 34.240.0.0/13 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IE |
| 34.242.185.233 | 34.240.0.0/13 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IE |
| 34.250.244.98 | 34.248.0.0/13 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IE |
| 34.253.140.134 | 34.248.0.0/13 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IE |
| 54.154.221.92 | 54.154.0.0/16 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IE |
| 54.171.209.7 | 54.171.0.0/16 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IE |
| 54.195.171.157 | 54.195.0.0/16 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IE |
| 54.208.26.124 | 54.208.0.0/15 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 54.229.126.57 | 54.229.0.0/17 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IE |
| 54.76.94.70 | 54.76.0.0/15 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IE |
| 63.33.102.222 | 63.32.0.0/14 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IE |
| 99.81.116.106 | 99.80.0.0/15 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IE |
WHOIS identity
WHOIS data is temporarily unavailable. Refresh in a moment to retry.
Subdomains
Subdomain count is temporarily unavailable. Refresh in a moment to retry.
Web-graph footprint
Distinct hostnames that link to or from argen.com in the public web crawl.
Threat posture
History
Mail and authentication
MX records
SPF policy
5 SPF mechanisms authorising senders for argen.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | _spf.salesforce.com |
| SPF_INCLUDE | et._spf.pardot.com |
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_IP | 208.75.120.0/22 |
| SPF_IP | 38.107.163.123 |
Related pages
Pivot deeper into the graph from argen.com.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "argen.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.