Registered
- peoples.
ru - Nov 3, 1999 — 26 years old
- people.
com - Jun 2, 1994 — 32 years old
Compare two sites
Paste the link you were sent and the brand it claims to be.
AboutUs puts the two domains side by side — registration, DNS, HTTPS, email authentication, and Authority/Safety — so you can see what's actually different before you click through.
What's different
- Registered 26 years old vs 32 years old.
- Different registrar — peoples.ru: REGRU-RU; people.com: MarkMonitor Inc..
- Different nameservers — peoples.ru uses an unidentified provider; people.com uses an unidentified provider.
Side-by-side facts for peoples.ru and people.com
Registrar
- peoples.
ru - REGRU-RU
- people.
com - MarkMonitor Inc.
Nameservers / DNS provider
- peoples.
ru - ns1.reg.ru, ns2.reg.ru
- people.
com - blue.foundationdns.com, blue.foundationdns.org
HTTPS / certificate
- peoples.
ru - The website responded over HTTPS. Certificate issued by Let's Encrypt (expires Dec 4, 2026).
- people.
com - The website responded, but not with a successful status. Certificate issued by Let's Encrypt (expires Nov 12, 2026).
Email authentication
- peoples.
ru - SPF record not found; DMARC record found.
- people.
com - SPF record not found; DMARC record found.
Authority / Safety
- peoples.
ru - Authority: not enough signals yet. Safety 90/100 (Clear).
- people.
com - Authority 83/100. Safety 90/100 (Clear).
Verified-owner status
- peoples.
ru - Claimable
- people.
com - Claimable
AboutUs on record since
- peoples.
ru - Since 2006
- people.
com - Since 2006
| Fact | peoples. | people. |
|---|---|---|
| Registered | Nov 3, 1999 — 26 years old | Jun 2, 1994 — 32 years old |
| Registrar | REGRU-RU | MarkMonitor Inc. |
| Nameservers / DNS provider | ns1.reg.ru, ns2.reg.ru | blue.foundationdns.com, blue.foundationdns.org |
| HTTPS / certificate | The website responded over HTTPS. Certificate issued by Let's Encrypt (expires Dec 4, 2026). | The website responded, but not with a successful status. Certificate issued by Let's Encrypt (expires Nov 12, 2026). |
| Email authentication | SPF record not found; DMARC record found. | SPF record not found; DMARC record found. |
| Authority / Safety | Authority: not enough signals yet. Safety 90/100 (Clear). | Authority 83/100. Safety 90/100 (Clear). |
| Verified-owner status | Claimable | Claimable |
| AboutUs on record since | Since 2006 | Since 2006 |
What to do next
Go to the brand's site by typing the address yourself, or use a bookmark you saved before — never the link from the message. If you already clicked through and entered anything, act on it now:
- Your bank or card issuerAlready paid or shared card details? Call the number on your card and ask to dispute the charge or freeze the card — do this first, before anything else here.
- FTC — reportfraud.ftc.gov The US Federal Trade Commission takes consumer fraud reports here. Outside the US, your country's consumer-protection agency is the equivalent.
- Google Safe Browsing Report a phishing or malware page so Chrome, Firefox, and Safari can warn the next person who visits it.