Hostname
lifesite.net
Last fetched
lifesite.net resolves to 104.21.62.224, announced in 104.21.48.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. lifesite.net is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 104.21.62.224
104.21.48.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.139.214
172.67.128.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.96.3
188.114.96.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.97.3
188.114.97.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:617
- Registrant organisation
- anonymize, llc.
- Contact emails
- lifesite.net-1hrdqtpsmsylz@anonymize.com, lifesite.net-1hv0hrqt561ip@anonymize.com, lifesite.net-1ib0e7ysb3qk4@anonymize.com, lifesite.net-1iv11v9ewnktz@anonymize.com, lifesite.net-1jer1ri24j1b5@anonymize.com, lifesite.net-1jetsdghswy0o@anonymize.com, lifesite.net-qhsuvrf9lso3@anonymize.com, lifesite.net-r1dd3wu6g4e1@anonymize.com, lifesite.net-rhiua1sksin7@anonymize.com, lifesite.net-rkwtijeasfna@anonymize.com, lifesite.net-t4w78cfqiybc@anonymize.com, lifesite.net-t844m60yw8yq@anonymize.com, lifesite.net-trz57fdlclrl@anonymize.com, lifesite.net-ublw448gmezl@anonymize.com, lifesite.net-urmucv9p2rtt@anonymize.com, lifesite.net@anonymize.com, lifesite.net@domainnameproxyservice.com, sjalsevac@lifesitenews.com
Subdomains
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Mail and authentication
Nameservers
- jim.ns.cloudflare.com
- kim.ns.cloudflare.com
MX records
- mail1.lifesitenews.com
SPF policy
- include: spf.protection.outlook.com
- include: mta.lifesite.net
- ip: 135.148.132.81
Threat-feed evidence
History
Related pages
Pivot from lifesite.net into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "lifesite.net"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.