Hostname
angi.com
Last fetched
angi.com resolves to 2 IPv4 addresses operated by CLOUDFLARENET - Cloudflare, Inc. in CA. WHOIS lists iana:146 as the registrar.
Nutrition Label
Resolution chain
angi.com resolves to 2 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 104.18.41.15 | 104.18.41.0/24 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 172.64.146.241 | 172.64.146.0/24 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
WHOIS identity
- Registrar
- iana:146
- Organization
- angi
- Contact emails
Subdomains
52 observed subdomains of angi.com.
Showing 25 of 52. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from angi.com in the public web crawl.
18,998 sites link to this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
32 SPF mechanisms authorising senders for angi.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | _spf.google.com |
| SPF_INCLUDE | _spf.salesforce.com |
| SPF_INCLUDE | sendgrid.net |
| SPF_INCLUDE | trustpilotservice.com |
| SPF_IP | 13.111.0.0/16 |
| SPF_IP | 13.127.153.86/32 |
| SPF_IP | 13.127.210.61/32 |
| SPF_IP | 135.84.68.123/32 |
| SPF_IP | 136.147.135.0/24 |
| SPF_IP | 136.147.176.0/24 |
| SPF_IP | 136.147.182.0/24 |
| SPF_IP | 167.89.127.244/32 |
| SPF_IP | 167.89.31.27/32 |
| SPF_IP | 167.89.4.33 |
| SPF_IP | 167.89.4.34 |
| SPF_IP | 167.89.4.35 |
| SPF_IP | 167.89.4.82 |
| SPF_IP | 168.238.194.7/32 |
| SPF_IP | 198.21.4.52/32 |
| SPF_IP | 198.245.81.0/24 |
| SPF_IP | 199.122.123.0/24 |
| SPF_IP | 208.86.168.7/32 |
| SPF_IP | 3.120.181.200/29 |
| SPF_IP | 3.222.0.24/29 |
| SPF_IP | 3.25.47.0/29 |
| SPF_IP | 3.7.25.40/29 |
| SPF_IP | 44.235.247.155 |
| SPF_IP | 52.12.244.9 |
| SPF_IP | 52.37.56.227 |
| SPF_IP | 52.66.154.99/32 |
| SPF_IP | 54.202.202.57 |
| SPF_IP | 74.63.151.39 |
Related pages
Pivot deeper into the graph from angi.com.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "angi.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.