Hostname
instakink.com
Last fetched
instakink.com resolves to 104.21.10.51, announced in 104.21.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. instakink.com is listed by 1 threat feed; reconciled level MEDIUM.
Threat posture
24threat score (procedure-native scale)
MEDIUMListed by 1 threat feed. Advisory: popularity-trust-offset.
- Threat feeds listing this
- 1
- Verdict coverage
- malicious-evidenced
- First seen on a feed
- Wed, 26 Aug 2026 14:51:25 GMT
- Last seen on a feed
- Sun, 13 Sep 2026 23:27:23 GMT
Nutrition Label
Resolution chain
- 104.21.10.51
104.21.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.162.46
172.67.160.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:1449
- Registrant organisation
- domain may be for sale, check afternic.com domain admin
- Contact emails
- instakink.com.1kt8rgk9evjlk@domains-anonymizer.com, instakink.com.2dnat0ke7x9l3@domains-anonymizer.com, instakink.com.2l8864tydakts@domains-anonymizer.com, instakink.com.2w7l390e2qfu1@domains-anonymizer.com, instakink.com.3pbv1yqbfkmfr@domains-anonymizer.com, instakink.com.3r7o9hpz9vf9f@domains-anonymizer.com, instakink.com.3t9500b7rbf3c@domains-anonymizer.com, instakink.com.8m5fcbnlotuf@domains-anonymizer.com, admin@domainregistriesfoundation.com, instakink.com.fjxvqdcnuoqy@domains-anonymizer.com, instakink.com.r4srs94p4ta4@domains-anonymizer.com, instakink.com@whoisprotectservice.net
Subdomains
Showing 12 of 418. View all subdomains →
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
Mail and authentication
Nameservers
- cheryl.ns.cloudflare.com
- lee.ns.cloudflare.com
Threat-feed evidence
History
Related pages
Pivot from instakink.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: "instakink.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.