mirror of
https://github.com/yogeshojha/rengine.git
synced 2026-10-20 15:21:30 +02:00
Yogesh OjhaandClaude Opus 5
8e2d57e8c6
Target correlation returned nothing for every target in a real project, and three of its four signals could not have worked. A registrant is matched on what two records must share to be the same party: case, punctuation and the company suffix are stripped by `registrant_key`, whose SQL half sits beside it (`registrant_key_sql`) because a match invisible to one half is a relation that never appears. Both halves refuse a redacted name, so "Redacted for Privacy" cannot group every privacy-protected domain in the instance into one false cluster. Measured on shopify.com and shopifycloud.com: one relation, on the registrant, and nothing between the four unrelated estates beside them. A registrar is dropped as a correlation. MarkMonitor registers for thousands of unrelated brands, so "same registrar" asserts nothing - shopify.com and uber.com share it and are not related. It stays available as a deliberate lookup in the correlation dialog, which is a question the operator asks, not a relation reNgine claims. The case-sensitive exact match it used would have missed those two anyway: `MarkMonitor Inc.` against `Markmonitor Inc.`. A nameserver is the one strong signal here - `a.ns.hackerone.com` is identifying, `gold.foundationdns.com` is Cloudflare's enterprise DNS and identifies nothing. Fifteen managed providers join the suppression list, foundationdns and markmonitor among them. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YYop31s6BqDUt4TBs5mbwa