Hostname
pipelinersales.com
Last fetched
pipelinersales.com resolves to 12 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in DE.
Nutrition Label
Resolution chain
pipelinersales.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 |
|---|---|---|---|---|
| 108.138.7.124 | 108.138.0.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 108.138.7.44 | 108.138.0.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 108.138.7.6 | 108.138.0.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 108.138.7.78 | 108.138.0.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 3.175.207.112 | 3.175.206.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | HK |
| 3.175.207.14 | 3.175.206.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | HK |
| 3.175.207.43 | 3.175.206.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | HK |
| 3.175.207.74 | 3.175.206.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | HK |
| 52.85.193.128 | 52.85.192.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.85.193.44 | 52.85.192.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.85.193.52 | 52.85.192.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.85.193.90 | 52.85.192.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
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 pipelinersales.com in the public web crawl.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
4 SPF mechanisms authorising senders for pipelinersales.com.
| Mechanism | Target |
|---|---|
| SPF_A | o4.ptr7857.pipelinersales.com |
| SPF_INCLUDE | _spf.google.com |
| SPF_INCLUDE | amazonses.com |
| SPF_INCLUDE | spf.protection.outlook.com |
Related pages
Pivot deeper into the graph from pipelinersales.com.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "pipelinersales.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.