Registered
- blogher.
com - Oct 21, 2003 — 22 years old
- blogger.
com - Jun 22, 1999 — 27 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 22 years old vs 27 years old.
- Different nameservers — blogher.com uses Amazon Route 53; blogger.com uses an unidentified provider.
- Authority 59/100 vs 87/100.
Side-by-side facts for blogher.com and blogger.com
Registrar
- blogher.
com - MarkMonitor Inc.
- blogger.
com - MarkMonitor Inc.
Nameservers / DNS provider
- blogher.
com - ns-41.awsdns-05.com, ns-701.awsdns-23.net (Amazon Route 53)
- blogger.
com - ns2.google.com, ns4.google.com
HTTPS / certificate
- blogher.
com - The website responded over HTTPS. Certificate issued by Let's Encrypt (expires Nov 5, 2026).
- blogger.
com - Too many redirects during the trust-signal check. Certificate issued by Google Trust Services (expires Dec 3, 2026).
Email authentication
- blogher.
com - SPF record not found; DMARC record not found.
- blogger.
com - SPF record not found; DMARC record found.
Authority / Safety
- blogher.
com - Authority 59/100. Safety 90/100 (Clear).
- blogger.
com - Authority 87/100. Safety 90/100 (Clear).
Verified-owner status
- blogher.
com - Claimable
- blogger.
com - Claimable
AboutUs on record since
- blogher.
com - Since 2007
- blogger.
com - Since 2007
| Fact | blogher. | blogger. |
|---|---|---|
| Registered | Oct 21, 2003 — 22 years old | Jun 22, 1999 — 27 years old |
| Registrar | MarkMonitor Inc. | MarkMonitor Inc. |
| Nameservers / DNS provider | ns-41.awsdns-05.com, ns-701.awsdns-23.net (Amazon Route 53) | ns2.google.com, ns4.google.com |
| HTTPS / certificate | The website responded over HTTPS. Certificate issued by Let's Encrypt (expires Nov 5, 2026). | Too many redirects during the trust-signal check. Certificate issued by Google Trust Services (expires Dec 3, 2026). |
| Email authentication | SPF record not found; DMARC record not found. | SPF record not found; DMARC record found. |
| Authority / Safety | Authority 59/100. Safety 90/100 (Clear). | Authority 87/100. Safety 90/100 (Clear). |
| Verified-owner status | Claimable | Claimable |
| AboutUs on record since | Since 2007 | Since 2007 |
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.