We Disrupt Cybercrime with Dark Web Intelligence
Our mission is to make the internet safer with automated dark web monitoringsolutions that help businesses disrupt cybercrime together with our customers and partners, we aim to end criminals' ability to profit from stolen information.
Our Mission
Our Mission: Making the Internet Safer with Dark Web Intelligence
DARKX leadership team brings a wealth of experience from Fortune 500 companies, threat intelligence vendors, federal agencies, and enterprise security teams.
We correlate dark web data to help organisations understand identity exposure and prevent targeted attacks including ransomware, credential theft, phishing, and account compromise. You can check your identity exposure with the Breach Tracker.
Our platform delivers actionable intelligence, not noise. Every alert is enriched with context so your team can respond with precision.
By the numbers
DarkX by the Numbers: 500+ Customers, 700B+ Identity Records
Read about our security and compliance standards.
What we do
What DarkX Does: Dark Web Monitoring & Threat Detection
Comprehensive Scanning
From exposed endpoints to misconfigured services, we scan it all.
Learn more about our scanning →Dark Web Intelligence
Monitor leaked credentials, forums, and underground chatter.
Leaked credential monitoring →TLS Security Checks
Validate SSL/TLS configurations and identify weaknesses.
Attack Surface Mapping
Discover unknown assets and reduce your blind spots.
Learn more about our scanning →Ready to get started? View DarkX pricing plans.
About DarkX: FAQs
Yes. The transition period deadline for TCF v2.3 is 28 February 2026, so your current setup should allow for supporting v2.3 rather than v2.2. The only significant change is that the Disclosed Vendors segment is now a mandatory part of the TC String. You should ask your CMP if it is updated.
It is a part of the TC String that specifies whether a specific vendor was disclosed to the user in the CMP interface. It is intended to eliminate uncertainty for vendors that rely on legitimate interest as a legal basis for processing. It is mandatory in TCF v2.3.
TCF is voluntary, but it is designed for publishers and ad-tech vendors, CMPs, and other marketing professionals involved in programmatic advertising in Europe. You probably need it if you advertise there or get your advertising services from European companies. If you do not use programmatic advertising, you probably do not need it, but you still need to ensure that consent is obtained in accordance with the GDPR and ePrivacy regulations.
The regulation uses standard purposes as a unified language for describing the processing activities described in the CMP’s purpose strings. They are all about storing or accessing information on the user’s device, serving ads based on limited information, profiling, and measuring the performance of ads and content. Special Purposes and Features are separated from them.
You need to ensure that your CMP is IAB Europe-compliant, up-to-date, and properly configured according to the TCF policies. You can do that by checking whether you can reject all, partially allow, withdraw consent, and whether trackers are blocked by a “no” choice. A properly formed TC String is not sufficient.
You need to choose an ad-tech vendor that supports TCF v2.3, synchronize your vendors with the Global Vendor List, and configure the CMP to show purposes and vendors correctly. Then you have to make sure that you can generate a TC String that will be properly read by all vendors and that all trackers are disabled until consent is obtained. You also need to retest everything in accordance with updates to the framework.