Hostname

ripten.com

Last fetched Tue, 15 Sep 2026 02:51:36 GMT

ripten.com resolves to 104.26.10.88, announced in 104.26.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. ripten.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this: 0
Verdict coverage: known-clean

Nutrition Label

Resolution chain

104.26.10.88
104.26.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
104.26.11.88
104.26.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
172.234.24.211
172.234.16.0/20 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
172.239.57.117
172.239.32.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
172.67.70.213
172.67.64.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
23.94.141.9
23.94.141.0/24 · AS-COLOCROSSING - HostPapa · Elk Grove Village, US

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar: iana:1068
Registrant organisation: chady lakkis
Contact emails: chadylakkis@gmail.com, df6a69cb0c74443f94b5d631fc2ec186.protect@withheldforprivacy.com, fed5760722e64e2eb40c59728b2626f2.protect@withheldforprivacy.com

Subdomains

Subdomain
www.ripten.com

Showing 1 of 1 subdomain (1 per page).

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

kayden.ns.cloudflare.com
odin.ns.cloudflare.com
paige.ns.cloudflare.com
serenity.ns.cloudflare.com
dns1.registrar-servers.com
dns101.registrar-servers.com
dns102.registrar-servers.com
dns2.registrar-servers.com

MX records

mx.plingest.com

Threat-feed evidence

History

Pivot from ripten.com 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: "ripten.com"})-[: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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.