Registered
- nikken.
com - Dec 21, 1995 — 30 years old
- nikkei.
com - May 9, 1995 — 31 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 30 years old vs 31 years old.
- Different registrar — nikken.com: Network Solutions, LLC; nikkei.com: Japan Registry Services Co., Ltd..
- Different nameservers — nikken.com uses Cloudflare; nikkei.com uses Amazon Route 53.
Side-by-side facts for nikken.com and nikkei.com
Registrar
- nikken.
com - Network Solutions, LLC
- nikkei.
com - Japan Registry Services Co., Ltd.
Nameservers / DNS provider
- nikken.
com - ray.ns.cloudflare.com, cheryl.ns.cloudflare.com (Cloudflare)
- nikkei.
com - ns-59.awsdns-07.com, ns-1261.awsdns-29.org (Amazon Route 53)
HTTPS / certificate
- nikken.
com - The website responded over HTTPS.
- nikkei.
com - The website responded over HTTPS. Certificate issued by Amazon (expires Apr 9, 2027).
Email authentication
- nikken.
com - SPF record not found; DMARC record found.
- nikkei.
com - SPF record not found; DMARC record found.
Authority / Safety
- nikken.
com - Authority: not enough signals yet. Safety 90/100 (Clear).
- nikkei.
com - Authority 94/100. Safety 90/100 (Clear).
Verified-owner status
- nikken.
com - Claimable
- nikkei.
com - Claimable
AboutUs on record since
- nikken.
com - Not retrieved yet
- nikkei.
com - Since 2010
| Fact | nikken. | nikkei. |
|---|---|---|
| Registered | Dec 21, 1995 — 30 years old | May 9, 1995 — 31 years old |
| Registrar | Network Solutions, LLC | Japan Registry Services Co., Ltd. |
| Nameservers / DNS provider | ray.ns.cloudflare.com, cheryl.ns.cloudflare.com (Cloudflare) | ns-59.awsdns-07.com, ns-1261.awsdns-29.org (Amazon Route 53) |
| HTTPS / certificate | The website responded over HTTPS. | The website responded over HTTPS. Certificate issued by Amazon (expires Apr 9, 2027). |
| 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 94/100. Safety 90/100 (Clear). |
| Verified-owner status | Claimable | Claimable |
| AboutUs on record since | Not retrieved yet | Since 2010 |
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.