-</style></head><body class="article-offset lux"><header class="nav"><div class="container nav-inner nav-container-wide"><div class="brand"><img alt="Metridex" class="brand-logo" src="/logo/metridex_logo_header.png"/></div><nav class="nav-links"><a href="/articles.html">All articles</a><a href="videos.html">Videos</a><a href="help.html">Help</a></nav><div class="nav-actions"><button class="icon-btn" id="themeToggle" title="Toggle theme">🌙</button></div></div></header><section class="hero-subtle"><div class="container"><div class="flex-row space-between" style="display:flex; align-items:center; justify-content:space-between; gap:16px;"><div><h1 style="margin-top:0.25rem">WHOIS & Wayback checks</h1><div class="article-kicker">Guide · Sep 29, 2025</div><div class="article-author">— Omar Ahmad, Founder of Metridex</div><div class="article-body"></div></div></div></div></section><section class="section"><div class="container article"><!-- EN --><div class="article-content" ><p><strong>TL;DR</strong>: domains and their history often expose “fast-fork” behavior or short-lived sites. We check WHOIS/RDAP, SSL chains, and Wayback snapshots to catch red flags early.</p><h2>1) WHOIS/RDAP: age and stewardship</h2><p>Young domains aren’t a crime — but they correlate with higher risk when paired with other signals. We read registrar, creation date, and changes. Sudden registrar hops are a smell.</p><h2>2) SSL: minimal hygiene baseline</h2><p>A valid TLS chain with sane expiry doesn’t mean “safe” — but broken or self-signed certs are a clear baseline fail. We surface issuer and expiry to spot neglect.</p><h2>3) Wayback: time is a moat</h2><p>Snapshots indicate persistence. No snapshots on an “established” brand? Suspicious. A handful of recent snapshots for a new token site? Acceptable, but note it.</p><div class="tip"><strong>Tip:</strong> combine website hygiene with on-chain context: if LP is thin and domain is brand new with no snapshots, slow down.</div><h2>4) Common red flags</h2><ul><li>Brand-new domain + aggressive marketing + thin LP.</li><li>Registrar changes clustered around token launch.</li><li>Mismatch between site domain and links embedded in social posts.</li><li>SSL expiring in days or issued by dubious CAs.</li></ul><h2>5) In QuickScan</h2><p>We fetch WHOIS/RDAP, SSL issuer/expiry, and Wayback presence for the provided site. Signals are folded into the verdict via <em>Why++</em>.</p><hr/><p><strong>Try it</strong>: <a href="https://t.me/MetridexBot" rel="noopener" target="_blank">@MetridexBot</a> • <a href="https://metridex.com" rel="noopener" target="_blank">metridex.com</a></p></div><!-- RU --><h2>4) Частые красные флаги</h2><ul><li>Совсем новый домен + агрессивный маркетинг + тонкий LP.</li><li>Смена регистратора вокруг даты запуска токена.</li><li>Несоответствие домена сайта ссылкам в соцсетях.</li><li>SSL скоро истекает или выдан сомнительным УЦ.</li></ul><h2>5) В QuickScan</h2><p>Мы подтягиваем WHOIS/RDAP, издателя/срок SSL и наличие снимков Wayback для сайта из карточки. Сигналы учитываются в вердикте через <em>Why++</em>.</p><hr/><p><strong>Попробовать</strong>: <a href="https://t.me/MetridexBot" rel="noopener" target="_blank">@MetridexBot</a> • <a href="https://metridex.com" rel="noopener" target="_blank">metridex.com</a></p></div></div></section><footer class="footer"><div class="container"><p>© <span id="year"></span> Metridex.</p></div></footer><div class="article-nav"><a href="/articles.html">← Back to Articles</a><a href="/article-quickscan-methodology_bilingual_v3.html">← Prev: QuickScan methodology</a><a href="/article-signals-whyplusplus_bilingual_v1.html">Next: Signals & Why++ →</a></div><script>(function(){
0 commit comments