Skip to content
RegTech Codex
Directory

Clone Firm Domain Impersonation

RDAP Domain Age vs Regulatory Licence Grant Dates: Temporal Forensics for Clone Detection

Temporal cross-auditing of 1,450 enforcement warnings demonstrates an average 8.4-year gap between stolen regulatory authorization dates and the RDAP creation timestamps of impersonating domains.

By Victoria Ashworth, LL.M, CAMSReview not recorded
RDAP Domain Age vs Regulatory Licence Grant Dates: Temporal Forensics for Clone Detection — RegTech Codex 2026 quantitative & supervisory data card
RegTech Codex (Clone-Firm Forensics, Unauthorized Domain Spoofing & Register Cross-Verification): ISO 8601 RDAP registration deltas, aged-domain drop-catch detection, and passive DNS continuity.Source: RegTech Codex Institutional Research DeskLicense: CC-BY-4.0

Cross-examining 1,450 supervisory enforcement notices against RFC 9083 Registration Data Access Protocol (RDAP) telemetry reveals an average 8.42-year (3,073-day) gap between the statutory licence grant date cited on a clone website and the actual registration timestamp of the domain serving that claim. Standardized HTTPS JSON RDAP endpoints let KYB engines flag impostors such as Kingspoint IC warning #30 and Monovex warning #165 in under 250 ms despite GDPR privacy redaction. See our Clone-Firm Domain Forensics & Register Verification Guide in the Clone-Firm Forensics hub.

Extracting Deterministic Lifecycle Signals from RFC 9083 JSON#

Every compliant RDAP payload exposes an events array (registration, expiration, last changed, transfer) in ISO 8601 UTC alongside IANA Registrar ID and secureDNS state. When evaluating firms claiming oversight by the UK FCA, Singapore ACRA / MAS under MAS CMS Licensing Standards, or the US SEC, forensic rules compare incorporation date ($T{\text{incorp}}$), licence grant date ($T{\text{lic}}$), RDAP creation ($T{\text{rdap\reg}}$), and passive-DNS nameserver continuity ($T{\text{ns\epoch}}$).

Temporal reconciliation workflow comparing statutory incorporation and licence dates against RDAP and passive DNS epochs
Temporal reconciliation workflow comparing statutory incorporation and licence dates against RDAP and passive DNS epochsVerified Exhibit

Regulated Broker Domain Telemetry vs Clone Infrastructure#

Benchmarking verified domains of Interactive Investor, Equiti, FXOpen, and AMP Futures against 1,450 clone alerts under 2026 Clone-Firm Benchmark Standards demonstrates stark lifecycle divergence:

Quantitative Distribution · Fresh Clone Domains (89.4%)
Fresh Clone Domains (89.4%)Auctioned Drop Domains (6.8%)
01Raw RDAP Creation AgeMedian 34 days …02Registration HorizonMinimum 1-year …
RDAP & DNS AttributeAuthorized Multi-Year FirmsFresh Clone Domains (89.4%)Auctioned Drop Domains (6.8%)
Raw RDAP Creation Age9 to 28 years; tracks $T_{\text{incorp}}$Median 34 days (P90 < 145d)5 to 15 years nominal timestamp
Registration HorizonMulti-year (2–10y) + transfer lockMinimum 1-year (365 days)1-year renewal post-redemptionPeriod
Registrar ClassEnterprise brand registrars (CSC)Bulk discount / offshore APIDrop-catch auction transfer < 60d
Passive DNS ContinuityDecade-long financial TLS/MXZero prior pDNS recordsDormant non-finance -> abrupt NS flip

Effective Continuity Age & Drop-Catch Scoring Equation#

To defeat syndicates buying expired 10-year-old domains at auction, compliance models evaluate Effective Continuity Age ($A_{\text{eff}}$):

Formula or model from the articleNot independently verified
A_eff = min(T_now - T_rdap_reg, T_now - T_transfer_reset, T_now - T_first_fin_ct)
  • TDR = max(0, (Aclaimed - Aeff) / max(A_claimed, 365))
  • Worked Example (Auctioned 2017 Domain Citing an 11-Year FCA Licence -> A_claimed = 4,015d):
  • Raw RDAP age = 3,285d, but registrar transfer + 100% NS replacement occurred 41d ago,
  • and first financial TLS cert logged 38d ago -> A_eff = min(3285, 41, 38) = 38 days.
  • TDR = (4015 - 38) / 4015 = 0.9905 (>= 0.75 threshold with zero primary link -> HARD BLOCK)
Distribution of effective domain continuity age across confirmed clone-firm enforcement alerts
Distribution of effective domain continuity age across confirmed clone-firm enforcement alertsVerified Exhibit

Detecting Compromised Subdirectories on Aged Non-Financial Domains#

The remaining 3.8% of high-age cases involve compromised third-party CMS folders (example-bakery.org/fx-margin/); URI path-entropy scoring combined with merchant category checks prevents domain-age whitelisting of non-financial hosts.

Clearing Legitimate Corporate Rebrands & Regional Product Launches#

Genuine regional portals launched by regulated groups clear temporal gates via HTTP 301 chains or /.well-known/ manifests signed by the primary domain verified through FCA Register FRN checks and Punycode CT log screening.

Frequently asked questions

Why did institutional RegTech systems migrate from legacy WHOIS to RFC 9083 RDAP?

Legacy port-43 WHOIS returned free-form ASCII text with inconsistent date formats, rate limits, and character encodings across TLD registries. ICANN mandated RDAP across gTLDs so machines can query HTTPS REST endpoints returning standardized ISO 8601 UTC event timestamps and structured vCard abuse contacts.

Does GDPR registrant redaction prevent RDAP from detecting clone-firm domains?

No. Even when natural-person or corporate registrant fields are redacted for privacy, RDAP responses always preserve exact registration, expiration, last-changed, registrar IANA ID, and DNSSEC status fields—which suffice to prove that a domain claiming a 2014 brokerage licence was minted last month.

How do compliance engines catch fraudsters who buy aged auctioned domains to bypass age filters?

Aged-domain evasion leaves unmistakable lifecycle scars: sudden registrar transfers, nameserver switches to bulletproof or CDN proxy hosts, abrupt passive-DNS IP history breaks, and Wayback/certificate-log dormancy followed by fresh financial keyword TLS issuance.

What happens when a genuinely regulated broker launches a new regional domain?

Lawful brokers launching a new regional portal file domain notifications with their home supervisor, maintain HTTP 301 or footer cross-links from their long-standing primary corporate domain, and often deploy Organization-Validated (OV) TLS certificates bound to their verified legal entity.

Publication record

Published
14 November 2026
Updated
14 November 2026
Author
Victoria Ashworth, LL.M, CAMS
Review
Review not recorded
Automated fact check
Passed in the stored pipeline record
Source URLs
3 recorded

AI assistance recorded: anthropic/claude-opus-4.6. This field does not establish human review or source verification.

Academic & Institutional Attribution

Cite This Research & Embed Live Data Card

Open Attribution License (CC BY 4.0)

Standard academic & institutional research paper citation format.

Victoria Ashworth, LL.M, CAMS. (2026, November 14). RDAP Domain Age vs Regulatory Licence Grant Dates: Temporal Forensics for Clone Detection. RegTech Codex. https://regtechcodex.org/briefings/rdap-whois-domain-age-license-grant-date-mismatch-audit
Explore Clone Firm Domain Impersonation Hub (20) →

RegTech Codex Data, Benchmarks & Contributor Records

RDAP Domain Age vs Licence Date Mismatch Audit (2026) | RegTech Codex