Hostname
kittysplit.com
Last fetched
kittysplit.com resolves to 206.189.241.37, announced in 206.189.240.0/22 by DIGITALOCEAN-ASN - DigitalOcean, LLC in NL. kittysplit.com 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
- 206.189.241.37
206.189.240.0/22 · DIGITALOCEAN-ASN - DigitalOcean, LLC · Amsterdam, NL
IPv6 resolution
No AAAA record for kittysplit.com is recorded in WhisperGraph.
Attribution
digitalocean
ORIGIN_AS
WHOIS identity
- Registrar
- iana:1387
- Registrant organisation
- c/o whoisproxy.com
- Contact emails
- h2672564@domains.namespace4you.com, qswxhbgmgs@whoisprivacyprotect.com, 1ab0b9cb64@kittysplit.com.whoistrustee.com, 1a1064aeba9e37a3417c747da0d00a46ec57f9abf429345d459ebdc02b279ab2@kittysplit.com.whoisproxy.org, 2631f9dc476aa98639349ae34d3215f7b4bb3c1915d8fe74180a391404a6951e@kittysplit.com.whoisproxy.org, 3380d145ef3b45597f7eed3c2b7c077c3098a26cd143bc6d5304c3967cffcd71@kittysplit.com.whoisproxy.org, 7ed728cf2228ad4ff0328e9f60bb26eadc7a3732c0836a1f6a514acedf4b4fbb@kittysplit.com.whoisproxy.org, 893b5f73d1043cc513bdcd3a10360c4d33f8334dac0c9edd7e8a85e9458e6874@kittysplit.com.whoisproxy.org, da0790c410ed6492eb94a85996ad130ed1cd6b84bf243e8410206bfd53b91802@kittysplit.com.whoisproxy.org, fb785903e37ffcc54340318cfd84aea2165d00826beb13de90861fd3359a10b4@kittysplit.com.whoisproxy.org
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
- ns1.digitalocean.com
- ns2.digitalocean.com
- ns3.digitalocean.com
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
SPF policy
- include: _spf.google.com
Threat-feed evidence
History
Related pages
Pivot from kittysplit.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: "kittysplit.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.