WebVetted
+ New  

Caxep Investigation Report

Generated: Jun 3, 2026

Create OSINT Report
Enable Monitor
Denis Kulakov Profile Picture

Denis Kulakov

Male Russian
Recommended Action
Proceed
Overall Summary
Safe
  Why we think so? 

The X account @caxep looks like a real, long-running personal profile for Denis Kulakov. ✅ It was created in 2008, is public, and shows steady historical activity, with a Moscow location and a Russian bio that fit the identity signal. The main limitation is that no tweet corpus was returned, so engagement quality and recent behavior are only partly observable.

Confidence Score Our overall confidence rating for this entity based on public signals, activity, and risk checks.
90%
Live Intel Map

Risks Identified

🛡️

Identity looks coherent

  • The X handle @caxep matches Denis Kulakov exactly.
  • The account dates back to 2008, which supports continuity.
  • A Moscow location and Russian bio fit the same identity signal.
📉

Audience is small, so engagement is harder to read

  • Follower count is 248, with 291 following.
  • No tweet corpus was returned for content-level engagement analysis.
  • Authority is limited, even if the profile itself looks authentic.

Linked Telegram domain looks clean

  • The bio links to t.me/watch_it.
  • No Safe Browsing risk was detected for t.me.
  • WHOIS data shows a long-established domain with normal DNS and SSL records.

Account Insights

Real Person? Yes
Reputation Moderate
Follower engagement Moderate
Quality of Posts Moderate
Posting Frequency High
Reach & influence Poor


Red Flags & Warnings

  • No tweet corpus was returned, so recent behavior and content themes could not be reviewed.
  • Follower count is modest at 248, which limits authority and makes audience assessment less reliable.
  • Secondary identity matches exist, but they are not strong enough to confirm cross-platform ownership.

What's Good?

  • The account is old, public, and has a long posting history dating back to 2008.
  • The profile name exactly matches the target name Denis Kulakov.
  • The profile bio and Moscow location fit the identity context in the evidence.
  • No phishing or blacklist signal was detected for the linked Telegram domain t.me.

Visualize Denis Kulakov's entire online identity

Switch to the interactive graph to trace relationships instantly across 440 data points we collected.

Detailed Findings

Exact identity match to target name

Passed

"Strong anchor match from twitter_profile_v1 and person_social_search_v1."

Reason: The X profile name is Denis Kulakov, which matches the target name exactly.

Handle and profile continuity

Passed

"The social search result marks this as the primary match."

Reason: The handle caxep is directly tied to the named profile and is treated as the anchor account in the evidence set.

Profile age and activity history

Passed

"Older accounts with sustained use are generally more credible than recently created ones."

Reason: The account was created in 2008 and shows a long activity history with 8,795 posts and 696 media items.

Public footprint consistency

Passed

"This is supportive but not fully verified across other platforms."

Reason: The profile location is Moscow and the bio is in Russian, which fits the broader identity signals in the evidence.

External profile corroboration

Passed

"Secondary profiles are plausible leads, not confirmation by themselves."

Reason: Search results surface matching profiles on LinkedIn, Facebook, and Instagram, but only the X account is strongly corroborated.

Impersonation or scam indicators

Passed

"No threats were detected for the linked Telegram domain, and the profile is public and longstanding."

Reason: No direct scam, phishing, or impersonation signal was found in the available evidence.

Audience authenticity / engagement quality

Passed

"The evidence shows 248 followers and 291 following, but no tweet corpus was returned for deeper engagement analysis."

Reason: The account has modest follower volume and limited visible interaction data, so audience quality cannot be strongly assessed.

Interaction guidelines

Ice breakers

3 ideas

⤷ Click to view suggestions


  • I noticed your profile has been active since 2008 — what kind of posts have stayed most consistent for you?
  • Your bio is very minimal, but the Moscow location and Telegram link stood out. What do you usually share there?
  • You’ve had a long-running X account. Has your use of the platform changed much over the years?

Topics to Discuss

3 topics

⤷ Click to expand


  • public posts and long-term X activity
  • Russian-language bio and Moscow connection
  • Telegram link in the profile bio

Topics to Avoid

3 topics

⤷ Click to expand


  • asking for private contact details
  • trying to confirm ownership from weak secondary profiles alone
  • sensitive personal background not visible in public data

Key Evidence & Citations

⤷ 3 citations available


Best Action Plan

Recommended in-product follow-ups based on this report

Follow Up Questions

Ask anything on 440 data points collected for Denis Kulakov.

Sample questions

Click a card to start

Who is most likely behind this X account?
What profile link is connected to this account?
Which linked profiles look like the same person?
What are the strongest signs this account is authentic?

🕵🏻 Keep vetting

Analyst Briefing

Get answers grounded in the sourced data. Citations like will link to the evidence locker.

Evidence Locker
// Waiting for data ingestion...

Evidence Locked

This raw JSON payload contains sensitive intelligence data .

Unlock
440 data points collected