Registered
- te1egram.
cfd - Nov 1, 2026 — 3 days old
- telegram.
org - Dec 15, 2003 — 22 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 3 days old vs 22 years old.
- Different registrar — te1egram.cfd: NameSilo, LLC; telegram.org: GoDaddy.com, LLC.
Side-by-side facts for te1egram.cfd and telegram.org
Registrar
- te1egram.
cfd - NameSilo, LLC
- telegram.
org - GoDaddy.com, LLC
Nameservers / DNS provider
- te1egram.
cfd - Not retrieved yet
- telegram.
org - ns-cloud-b4.googledomains.com, ns-cloud-b1.googledomains.com
HTTPS / certificate
- te1egram.
cfd - No public A/AAAA record was found for this domain.
- telegram.
org - The website responded over HTTPS. Certificate issued by GoDaddy.com (expires Mar 11, 2027).
Email authentication
- te1egram.
cfd - SPF: not found in saved lookup · DMARC: not found in saved lookup.
- telegram.
org - SPF: record valid · DMARC: reject requested (p=reject).
Authority / Safety
- te1egram.
cfd - Authority: not enough signals yet. Safety: Not enough signals yet.
- telegram.
org - Authority 94/100. Safety 90/100 (Clear).
Verified-owner status
- te1egram.
cfd - Claimable
- telegram.
org - Claimable
AboutUs on record since
- te1egram.
cfd - Not retrieved yet
- telegram.
org - Since 2013
| Fact | te1egram. | telegram. |
|---|---|---|
| Registered | Nov 1, 2026 — 3 days old | Dec 15, 2003 — 22 years old |
| Registrar | NameSilo, LLC | GoDaddy.com, LLC |
| Nameservers / DNS provider | Not retrieved yet | ns-cloud-b4.googledomains.com, ns-cloud-b1.googledomains.com |
| HTTPS / certificate | No public A/AAAA record was found for this domain. | The website responded over HTTPS. Certificate issued by GoDaddy.com (expires Mar 11, 2027). |
| Email authentication | SPF: not found in saved lookup · DMARC: not found in saved lookup. | SPF: record valid · DMARC: reject requested (p=reject). |
| Authority / Safety | Authority: not enough signals yet. Safety: Not enough signals yet. | Authority 94/100. Safety 90/100 (Clear). |
| Verified-owner status | Claimable | Claimable |
| AboutUs on record since | Not retrieved yet | Since 2013 |
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.