March 2025 update
🌱March 2025 Update: We introduced tech stack detection, enhanced WHOIS parsing with registrant disclosure, a public identity graph for fraud analysis, expanded disposable phone detection, and time-based identity linkage counts across our APIs.
DOMAIN API — Domain Intelligence: Tech Stack Detection
What’s New
Our DOMAIN API now includes Tech Stack Detection within Domain Intelligence. This feature identifies the technologies used to build a website, such as web frameworks, analytics tools, content management systems, and e-commerce platforms.
Why It Matters
Understanding the tech stack behind a domain can provide critical context:
- A lack of technologies may signal a placeholder or non-legitimate website.
- The use of enterprise-grade tools often indicates credibility and investment in infrastructure.
Example Response
{
"domain": "example.com",
"tech_stack": [
"React",
"Cloudflare",
"Google Analytics",
"Shopify"
],
"tech_insight": "Uses multiple enterprise-grade technologies"
}
DOMAIN API — Enhanced WHOIS Parsing & Registrant Disclosure Detection
What’s New
Our DOMAIN API now features enhanced WHOIS data parsing and a new signal: Registrant Disclosed Detection. This update allows you to extract structured and reliable ownership metadata from WHOIS records with higher accuracy.
Key Improvements
- Detection of whether the registrant information is publicly disclosed
- Parsed WHOIS data including:
- Domain age
- Expiration and updated dates
- Registrant, Admin, and Technical contact details
Why It Matters
Exposed registrant information increases transparency, while anonymized or missing data can raise risk flags. The inclusion of domain age and expiration data helps assess domain maturity and potential for abuse.
Example Response
{
"domain": "example.com",
"registrant_disclosed": true,
"domain_age": "6 years ago",
"expiration_date": "2025-05-11",
"updated_date": "2024-05-27",
"registrant_organization": "ONEGREEN S R L",
"registrant_address": "Strada GORETTA, 90B, Mappano, TO, ITALY",
"admin_name": "Salvatore Incalcaterra",
"technical_organization": "ONEGREEN S R L"
}
CLOUD DASHBOARD — Public Graph Section for Identity Link Analysis
What’s New
Our internal identity graph is now publicly accessible via the CLOUD DASHBOARD. This new Graph Section visualizes suspicious relationships between identities, allowing customers to explore clusters and connections that could indicate fraud rings or multi-accounting behaviors.
Why It Matters
Understanding the context around an identity—such as shared devices, emails, or IP addresses—is critical in spotting collusion or synthetic networks. The graph provides:
- Visual insight into how identities are connected
- Indicators of risky clusters with high interconnectivity
- Enhanced ability to spot fraud rings, shared infrastructure, or identity farms
Example Use Case
An identity with 8 linked devices, 6 emails, and 3 shared IPs shows up in a dense cluster flagged for frequent account resets and high dispute rates—revealing potential organized fraud activity.
This feature transforms how you assess risk—moving from individual attributes to network-level insights.
PHONE API — Expanded Disposable Number Detection with New Scrapers
What’s New
We’ve expanded our detection capabilities for disposable and temporary phone numbers by integrating new scrapers targeting:
- Burner App
- TextBverified
Why It Matters
Detecting disposable phone numbers is critical for preventing account abuse, spam registrations, and fake verifications. These new sources improve our coverage of:
- Short-term number providers
- Fraud-friendly telecom services
- Identity obfuscation tools
Example Response
{
"claims": [
"phone"
],
"is_disposable": true,
"disposable_provider": "Burner App"
}
PHONE & EMAIL API — Time-Based Identity Linkage Counts
What’s New
We now provide time-scoped identity linkage counts within the PHONE & EMAIL API. In addition to lifetime linkages, you can now monitor:
- 7-day linkage count (high frequency = high risk)
- 120-day linkage count (medium-term behavioral insight)
Why It Matters
Lifetime identity linkages are useful but can be misleading without time context. A device linked to 50 identities over years may be benign—but 20 identities in a week? That’s suspicious.
Example Response
{
"claims": [
"email",
"phone"
],
email:{
"msisdn_identities_last_7_days_count": 18,
"msisdn_identities_last_120_days_count": 47,
"msisdn_identities_last_lifetime_days_count": 103
},
phone:{
"email_identities_last_7_days_count": 18,
"email_identities_last_120_days_count": 47,
"email_identities_last_lifetime_days_count": 103
}
}
📚 Resources
- Support Center - Assistance and answers from the Trustfull support team.
- Domain API Documentation - Information and guidelines on how to implement our Domain API.
- Phone API Documentation - More information on our Phone API.