Hostname
ipetitions.com
Last fetched
ipetitions.com resolves to 10 IPv4 addresses operated by AMAZON-AES - Amazon.com, Inc. in US. WHOIS lists iana:1068 as the registrar.
Nutrition Label
Resolution chain
ipetitions.com resolves to 10 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 100.25.55.142 | 100.24.0.0/13 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.213.216.111 | 3.208.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.218.96.40 | 3.208.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 34.197.171.119 | 34.192.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 44.214.203.191 | 44.192.0.0/11 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 52.3.114.180 | 52.2.0.0/15 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 54.197.61.118 | 54.196.0.0/15 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 13.216.132.13 | 13.216.0.0/13 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 32.195.97.32 | 32.192.0.0/14 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 100.49.13.156 | 100.48.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
WHOIS identity
- Registrar
- iana:1068
- Organization
- moniker privacy services
- Contact emails
- 265e29885be44a42b4f9ec47358bea2f.protect@whoisguard.com
- 6fd881fb369444ebbcc3fa05913966cb.protect@withheldforprivacy.com
- c92854b5f0f24fe89cad8909af9f1688.protect@withheldforprivacy.com
- ipetitions.com@monikerprivacy.net
- 5601c3f52ea1e2193416e2573fbfa2dc320b094a89028bdcc070307b6ec07fbf@ipetitions.com.whoisproxy.org
Subdomains
12 observed subdomains of ipetitions.com.
Web-graph footprint
Distinct hostnames that link to or from ipetitions.com in the public web crawl.
5,617 sites link to this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
1 SPF mechanism authorising senders for ipetitions.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | _spf.google.com |
Related pages
Pivot deeper into the graph from ipetitions.com.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "ipetitions.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.