Hostname
4life.com
Last fetched
4life.com resolves to 15 IPv4 addresses operated by CLOUDFLARENET - Cloudflare, Inc. in CA. WHOIS lists iana:292 as the registrar.
Nutrition Label
Resolution chain
4life.com resolves to 15 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 104.20.28.102 | 104.20.16.0/20 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 172.66.150.2 | 172.66.144.0/20 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 172.66.40.168 | 172.66.40.0/21 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 172.66.43.88 | 172.66.40.0/21 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 2.17.147.145 | 2.17.147.0/24 | AS20940 | AKAMAI-ASN1 | CZ |
| 2.17.147.192 | 2.17.147.0/24 | AS20940 | AKAMAI-ASN1 | CZ |
| 23.212.110.146 | 23.212.110.0/24 | AS20940 | AKAMAI-ASN1 | CZ |
| 23.212.110.168 | 23.212.110.0/24 | AS20940 | AKAMAI-ASN1 | CZ |
| 23.50.131.136 | 23.50.131.0/24 | AS20940 | AKAMAI-ASN1 | DE |
| 23.50.131.146 | 23.50.131.0/24 | AS20940 | AKAMAI-ASN1 | DE |
| 23.50.131.147 | 23.50.131.0/24 | AS20940 | AKAMAI-ASN1 | DE |
| 23.53.42.250 | 23.53.40.0/22 | AS20940 | AKAMAI-ASN1 | DE |
| 23.53.43.16 | 23.53.40.0/22 | AS20940 | AKAMAI-ASN1 | DE |
| 23.53.43.26 | 23.53.40.0/22 | AS20940 | AKAMAI-ASN1 | DE |
| 23.53.43.33 | 23.53.40.0/22 | AS20940 | AKAMAI-ASN1 | DE |
WHOIS identity
- Registrar
- iana:292
- Organization
- 4life research usa,
- Contact emails
Subdomains
138 observed subdomains of 4life.com.
Showing 25 of 138. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from 4life.com in the public web crawl.
279 sites link to this hostname.
Threat posture
History
Mail and authentication
SPF policy
3 SPF mechanisms authorising senders for 4life.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | spf1.4life.com |
| SPF_INCLUDE | spf2.4life.com |
| SPF_INCLUDE | spf3.4life.com |
Related pages
Pivot deeper into the graph from 4life.com.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "4life.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.