Skip to content

Commit e50899f

Browse files
omarakhmedov-webomarakhmedov-web
authored
Update article-whois-wayback_bilingual_v2.html
1 parent dc04cec commit e50899f

1 file changed

Lines changed: 75 additions & 69 deletions

File tree

‎article-whois-wayback_bilingual_v2.html‎

Lines changed: 75 additions & 69 deletions
Original file line numberDiff line numberDiff line change
@@ -1,71 +1,77 @@
1-
<!DOCTYPE html>
1+
<!doctype html>
2+
<html lang="en">
3+
<head>
4+
<meta charset="utf-8">
5+
<meta name="viewport" content="width=device-width, initial-scale=1">
6+
<title>WHOIS &amp; Wayback checks — Metridex</title>
7+
<meta name="description" content="Practical guide on verifying domains with WHOIS and the Wayback Machine to assess project credibility.">
8+
<link rel="stylesheet" href="/styles.css">
9+
<script src="/script.js" defer></script>
10+
</head>
11+
<body>
12+
<main class="article-content container" style="max-width:920px;margin:40px auto;padding:0 16px;">
13+
<header style="margin-bottom:20px;">
14+
<h1>WHOIS &amp; Wayback checks</h1>
15+
<p class="muted" style="opacity:.8;">Updated October 03, 2025</p>
16+
</header>
217

3-
<html lang="en"><head><meta charset="utf-8"/><meta content="width=device-width, initial-scale=1" name="viewport"/><title>Metridex — WHOIS &amp; Wayback checks</title><meta content="Why WHOIS/RDAP, SSL, and Wayback matter for token due diligence — article." name="description"/><link href="styles.css" rel="stylesheet"/><link href="/logo/favicon-32.png?v=3" rel="icon" sizes="32x32" type="image/png"/><link href="/logo/favicon-16.png?v=3" rel="icon" sizes="16x16" type="image/png"/><link href="/logo/apple-touch-icon.png?v=3" rel="apple-touch-icon" sizes="180x180"/><link href="/logo/favicon.ico?v=3" rel="icon"/><link href="/logo/site.webmanifest?v=3" rel="manifest"/><style>.article-meta{font-size:0.9rem;color:#9aa3af;margin:8px 0 18px}
4-
.article-nav{display:flex;gap:12px;flex-wrap:wrap;margin-top:28px}
5-
.article-nav a{padding:10px 14px;border:1px solid #2a2a2a;border-radius:10px;text-decoration:none}
6-
.article-nav a:hover{background:#0b0b0b}</style><style>.article-body{margin-top:56px}</style><style>.article-kicker{font-size:.9rem;color:#9aa3af;margin-top:8px}
7-
.article-author{font-size:.95rem;color:#c7cdd6;margin-top:6px}
8-
.article-body{margin-top:56px}</style><style>/* AURUM-DELTA: spacing under fixed header */
9-
.article-offset{padding-top:140px}
10-
/* visibility */
11-
.lang-block{display:none}
12-
.lang-block.active{display:block}
13-
.lang-switch{margin:10px 0 0;display:flex;gap:8px;align-items:center}
14-
.lang-switch button{padding:6px 10px;border:1px solid #2a2a2a;border-radius:8px;background:transparent;cursor:pointer}
15-
.lang-switch button.active{background:#0b0b0b}</style><style>
16-
/* AURUM-DELTA OVERRIDES — spacing + switcher visuals */
17-
.article-body{margin-top:8px !important} /* was ~56px; closer by ~1.5cm */
18-
.article-nav{margin-top:9px !important} /* was 28px; lifted by ~0.5cm */
18+
<section>
19+
<h2>Purpose</h2>
20+
<p>Use WHOIS and the Wayback Machine to quickly understand who is behind a domain, when it was created, and how the public website has evolved. This helps detect disposable websites, domain flipping, or attempts to hide past activity.</p>
21+
</section>
1922

20-
/* Language switcher: brighter, like homepage */
21-
.lang-switch{margin-top:10px; gap:10px}
22-
.lang-switch button{
23-
padding:8px 14px;
24-
border:1px solid #3b3b3b;
25-
border-radius:10px;
26-
background:rgba(255,255,255,0.04);
27-
color:#e5e7eb;
28-
font-weight:600;
29-
letter-spacing:.2px;
30-
}
31-
.lang-switch button:hover{background:rgba(255,255,255,0.08)}
32-
.lang-switch button.active{
33-
background:#1f2937;
34-
border-color:#6b7280;
35-
color:#ffffff;
36-
}
37-
</style><!-- MDX_EN_ONLY_NoBase -->
38-
</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 &amp; 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></section><footer class="footer"><div class="container"><p>© <span id="year"></span> Metridex.</p></div></footer><div class="article-nav"><a href="/article-quickscan-methodology_bilingual_v3.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 &amp; Why++ →</a></div><script>(function(){
39-
function switchTo(lang){
40-
document.documentElement.setAttribute('lang', lang);
41-
var blocks = document.querySelectorAll('.lang-block');
42-
blocks.forEach(function(el){
43-
if (el.classList.contains('lang-' + lang)){
44-
el.classList.add('active');
45-
el.style.display = 'block';
46-
} else {
47-
el.classList.remove('active');
48-
el.style.display = 'none';
49-
}
50-
});
51-
document.querySelectorAll('.lang-switch [data-lang]').forEach(function(btn){
52-
btn.classList.toggle('active', btn.getAttribute('data-lang')===lang);
53-
});
54-
try{ localStorage.setItem('lang', lang); }catch(e){}
55-
}
56-
var pref = 'en';
57-
try{
58-
var s = localStorage.getItem('lang');
59-
if (s === 'ru' || s === 'en') pref = s;
60-
}catch(e){}
61-
// initial
62-
switchTo(pref);
63-
// hook buttons
64-
document.addEventListener('click', function(e){
65-
var t = e.target;
66-
if (t && t.matches('.lang-switch [data-lang]')){
67-
e.preventDefault();
68-
switchTo(t.getAttribute('data-lang'));
69-
}
70-
});
71-
})();</script></body></html>
23+
<section>
24+
<h2>When to use</h2>
25+
<ul>
26+
<li>Before integrating a new partner, exchange, or service.</li>
27+
<li>When a project suddenly rebrands or “launches” on a fresh domain.</li>
28+
<li>If marketing claims don’t match the site’s age or history.</li>
29+
</ul>
30+
</section>
31+
32+
<section>
33+
<h2>Step‑by‑step</h2>
34+
<ol>
35+
<li><strong>WHOIS lookup.</strong> Check <em>creation date</em>, <em>registrar</em>, <em>nameservers</em>, and <em>registrant visibility</em>. Consistent infra over time is a good sign.</li>
36+
<li><strong>Wayback timeline.</strong> Open several snapshots (first, middle, latest). Compare the brand, product claims, and legal pages.</li>
37+
<li><strong>Cross‑signals.</strong> Compare domain age with Twitter/X account age, GitHub activity, mobile app release dates, and press mentions.</li>
38+
</ol>
39+
</section>
40+
41+
<section>
42+
<h2>Red flags</h2>
43+
<ul>
44+
<li>Domain registered very recently but project claims multi‑year history.</li>
45+
<li>Frequent switches of registrars and nameservers without clear reason.</li>
46+
<li>Wayback shows unrelated content (domain recycling) or aggressive post‑facto edits.</li>
47+
<li>Missing or constantly changing legal pages (ToS/Privacy/Company).</li>
48+
</ul>
49+
</section>
50+
51+
<section>
52+
<h2>Healthy signals</h2>
53+
<ul>
54+
<li>Older domain with consistent hosting and incremental site evolution.</li>
55+
<li>Stable legal pages and contact details that match filings and press.</li>
56+
<li>Past claims align with current product and team statements.</li>
57+
</ul>
58+
</section>
59+
60+
<section>
61+
<h2>Checklist</h2>
62+
<ul>
63+
<li>Creation &amp; update dates make sense relative to the roadmap.</li>
64+
<li>Registrars/nameservers stable (or changes are explained by growth).</li>
65+
<li>Historic snapshots contain the same brand and value proposition.</li>
66+
<li>Legal pages present and consistent.</li>
67+
</ul>
68+
</section>
69+
70+
<footer class="article-nav" style="display:flex;gap:12px;justify-content:space-between;align-items:center;margin:36px 0 24px;">
71+
<a class="btn prev" href="/article-quickscan-methodology_bilingual_v3.html">← Previous: QuickScan methodology</a>
72+
<a class="btn all" href="/articles.html">All articles</a>
73+
<a class="btn next" href="/article-signals-whyplusplus_bilingual_v1.html">Next: Signals &amp; Why++ →</a>
74+
</footer>
75+
</main>
76+
</body>
77+
</html>

0 commit comments

Comments
 (0)