Verifying against the live site and live WHOIS/DNS…
Common questions
Is blogcn.com legit or a scam?
blogcn.com was registered Nov 22, 2002 (23 years old), per public registration records. AboutUs doesn't label sites "legit" or "a scam": this page lists the dated registration, DNS, HTTPS, mail-authentication and safety checks we could verify, each with its source, so you can decide for yourself.
Who owns blogcn.com?
Nobody has completed AboutUs's owner verification for blogcn.com. That's true of most sites here — it isn't itself a warning sign.
When was blogcn.com registered?
blogcn.com's registration dates to Nov 22, 2002 (23 years old), per public registration records. Xiamen 35.com Information Co., Ltd. is the registrar on record today.
Correct a description, link or other detail. Submissions are reviewed before publication.
Lifeline · blogcn.com over time
Checked in the last 30 daysOlder, dated recordFrom registration records
Registered 23 years ago · on AboutUs since 2006 · 2 registrar changes since Jul 2, 2011 · 8 registrant changes since 2007 · last checked Nov 15, 2026.
Registration
RegisteredNov 22, 2002blogcn.com was registered on Nov 22, 2002.Source: RDAP, fetched Nov 10, 2026
AboutUs record
AboutUs wiki pageJun 19, 2006 – Apr 22, 2010An AboutUs wiki page described blogcn.com from Jun 19, 2006 to Apr 22, 2010 (5 edits).Source: AboutUs wiki archive, 2006–2023Current AboutUs record
Registrar
35 TECHNOLOGY CO., LTDJul 2, 2011 – Sep 21, 2012Registrar 35 TECHNOLOGY CO., LTD in the WHOIS and RDAP records held for blogcn.com, from Jul 2, 2011 to Sep 21, 2012.Source: WHOIS / RDAP archive (who.is)Xiamen 35.Com Technology Co., Ltd
Registrant
Registrant recordsMay 11, 2007 – Jun 4, 2026Registration records for blogcn.com are held from May 11, 2007 to Jun 4, 2026 (1,286 records). 8 changes of registrant name or organization are marked. Privacy-service and redaction changes, renames of the same organization and new contacts at it are not counted.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Zone file
Nameservers: blogcndns.comMay 11, 2007 – Jan 1, 2010Registration records listed blogcndns.com nameservers (nsbj.blogcndns.com) for blogcn.com from May 11, 2007 to Jan 1, 2010.Source: From registration records (WHOIS / RDAP archive, who.is)
Certificate
Google Trust ServicesMay 9, 2026 – Nov 19, 2026 (latest)Google Trust Services issued 3 certificates for blogcn.com from May 9, 2026, the latest valid until Jan 31, 2027. Seen in use on Oct 5, 2026.Source: Certificate Transparency logs (AboutUs's own certificate-log reader); TLS check, Oct 5, 2026
20052010201520202025Apr ’26← last 12 months, drawn wider
Every dated fact on this lifeline (32)
Nov 22, 2002Registration: blogcn.com was registered on Nov 22, 2002.Source: RDAP, fetched Nov 10, 2026
Jun 19, 2006 – Apr 22, 2010AboutUs record: An AboutUs wiki page described blogcn.com from Jun 19, 2006 to Apr 22, 2010 (5 edits).Source: AboutUs wiki archive, 2006–2023
May 11, 2007 – Jun 4, 2026Registrant: Registration records for blogcn.com are held from May 11, 2007 to Jun 4, 2026 (1,286 records). 8 changes of registrant name or organization are marked. Privacy-service and redaction changes, renames of the same organization and new contacts at it are not counted.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
May 11, 2007 – Jan 1, 2010Zone file: Registration records listed blogcndns.com nameservers (nsbj.blogcndns.com) for blogcn.com from May 11, 2007 to Jan 1, 2010.Source: From registration records (WHOIS / RDAP archive, who.is)
Jan 1, 2010Registrant: The registrant name or organization in the registration record changed; first recorded Jan 1, 2010. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Jun 23, 2026 – Nov 10, 2026 (latest)
Authority and Safety last refreshed Nov 10, 2026.
Source: AboutUs checks
Xiamen 35.Com Technology Co., Ltd
Jul 26, 2016 – Apr 5, 2024
Registrar Xiamen 35.Com Technology Co., Ltd (IANA 1316) in the WHOIS and RDAP records held for blogcn.com, from Jul 26, 2016 to Apr 5, 2024.
Source: WHOIS / RDAP archive (who.is)
Xiamen 35.com Information Co., Ltd.Xiamen 35.com Information Co., Ltd.Aug 14, 2024 – Oct 11, 2026 (latest)Registrar Xiamen 35.com Information Co., Ltd. (IANA 4163) in the registration data recorded, first on Aug 14, 2024 and most recently on Oct 11, 2026.Source: RDAP, fetched Nov 10, 2026
Registrant changeJan 1, 2010The registrant name or organization in the registration record changed; first recorded Jan 1, 2010. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Registrant changeJan 23, 2010The registrant name or organization in the registration record changed; first recorded Jan 23, 2010. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Registrant changeFeb 28, 2010The registrant name or organization in the registration record changed; first recorded Feb 28, 2010. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Registrant changeJul 11, 2010The registrant name or organization in the registration record changed; first recorded Jul 11, 2010. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Registrant changeAug 3, 2010The registrant name or organization in the registration record changed; first recorded Aug 3, 2010. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Registrant changeJun 7, 2011The registrant name or organization in the registration record changed; first recorded Jun 7, 2011. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Registrant changeNov 18, 2011The registrant name or organization in the registration record changed; first recorded Nov 18, 2011. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Registrant changeJul 26, 2016The registrant name or organization in the registration record changed; first recorded Jul 26, 2016. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
8 registrant changes, 2007–2026
Nameservers: dns-diy.com
Jan 23, 2010 – Nov 23, 2010
Registration records listed dns-diy.com nameservers (ns1.dns-diy.com) for blogcn.com from Jan 23, 2010 to Nov 23, 2010.
Source: From registration records (WHOIS / RDAP archive, who.is)
DNS moved to dns-diy.comJan 23, 2010blogcn.com's nameservers moved from blogcndns.com to dns-diy.com between Jan 1, 2010 and Jan 23, 2010. Last seen at blogcndns.com: Jan 1, 2010 (registration record). First seen at dns-diy.com: Jan 23, 2010 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Nameservers: yo2wp.comDec 24, 2010 – Mar 27, 2011Registration records listed yo2wp.com nameservers (ns1.yo2wp.com) for blogcn.com from Dec 24, 2010 to Mar 27, 2011.Source: From registration records (WHOIS / RDAP archive, who.is)
DNS moved to yo2wp.comDec 24, 2010blogcn.com's nameservers moved from dns-diy.com to yo2wp.com between Nov 23, 2010 and Dec 24, 2010. Last seen at dns-diy.com: Nov 23, 2010 (registration record). First seen at yo2wp.com: Dec 24, 2010 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Nameservers: dns-diy.comApr 15, 2011 – Oct 13, 2013Registration records listed dns-diy.com nameservers (ns1.dns-diy.com) for blogcn.com from Apr 15, 2011 to Oct 13, 2013.Source: From registration records (WHOIS / RDAP archive, who.is)
DNS moved to dns-diy.comApr 15, 2011blogcn.com's nameservers moved from yo2wp.com to dns-diy.com between Mar 27, 2011 and Apr 15, 2011. Last seen at yo2wp.com: Mar 27, 2011 (registration record). First seen at dns-diy.com: Apr 15, 2011 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Nameservers: dns-diy.comOct 18, 2013 – Apr 1, 2016dns-diy.com (ns1.dns-diy.com, ns2.dns-diy.com, ns3.dns-diy.com…) were the nameservers listed for blogcn.com at every ICANN zone-file snapshot AboutUs holds from Oct 18, 2013 to Apr 1, 2016 (snapshots exist for only part of 2013–2018).Source: ICANN zone-file snapshots, 2013–2018 (legacy archive)
Nameservers: dnspod.netJul 26, 2016 – Apr 2, 2018Registration records listed dnspod.net nameservers (f1g1ns1.dnspod.net, f1g1ns2.dnspod.net) for blogcn.com from Jul 26, 2016 to Apr 2, 2018. Days a zone file covers are shown from the zone file instead.Source: From registration records (WHOIS / RDAP archive, who.is)
DNS moved to dnspod.netJul 26, 2016blogcn.com's nameservers moved from dns-diy.com to dnspod.net at some point between Apr 1, 2016 and Jul 26, 2016. Last seen at dns-diy.com: Apr 1, 2016 (ICANN zone-file snapshot). First seen at dnspod.net: Jul 26, 2016 (registration record). AboutUs holds no nameserver records for the 4 months in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (ICANN zone-file snapshot → registration record)
Nameservers: dnspod.netApr 3, 2018dnspod.net (f1g1ns1.dnspod.net, f1g1ns2.dnspod.net) were the nameservers listed for blogcn.com at every ICANN zone-file snapshot AboutUs holds from Apr 3, 2018 to Apr 3, 2018 (snapshots exist for only part of 2013–2018).Source: ICANN zone-file snapshots, 2013–2018 (legacy archive)
Nameservers: dnspod.netApr 4, 2018 – Oct 18, 2019Registration records listed dnspod.net nameservers (f1g1ns1.dnspod.net, f1g1ns2.dnspod.net) for blogcn.com from Apr 4, 2018 to Oct 18, 2019. Days a zone file covers are shown from the zone file instead.Source: From registration records (WHOIS / RDAP archive, who.is)
Nameservers: CloudflareNameservers: CloudflareNov 24, 2019 – Jun 4, 2026Registration records listed Cloudflare nameservers (greg.ns.cloudflare.com, zoe.ns.cloudflare.com) for blogcn.com from Nov 24, 2019 to Jun 4, 2026.Source: From registration records (WHOIS / RDAP archive, who.is)
DNS moved to CloudflareNov 24, 2019blogcn.com's nameservers moved from dnspod.net to Cloudflare between Oct 18, 2019 and Nov 24, 2019. Last seen at dnspod.net: Oct 18, 2019 (registration record). First seen at Cloudflare: Nov 24, 2019 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Seen in the .com zone fileSep 8, 2026 – Nov 15, 2026 (latest)First seen in the .com zone file records AboutUs holds on Sep 8, 2026; latest sighting Nov 15, 2026. Nameservers on Nov 15, 2026: greg.ns.cloudflare.com, zoe.ns.cloudflare.com.Source: ICANN CZDS zone file, snapshot Nov 15, 2026
Let's EncryptJun 2, 2026 – Nov 19, 2026Let's Encrypt issued 3 certificates for blogcn.com from Jun 2, 2026, the latest valid until Jan 6, 2027.Source: Certificate Transparency logs (AboutUs's own certificate-log reader)
Jan 23, 2010
Registrant: The registrant name or organization in the registration record changed; first recorded Jan 23, 2010. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Jan 23, 2010 – Nov 23, 2010Zone file: Registration records listed dns-diy.com nameservers (ns1.dns-diy.com) for blogcn.com from Jan 23, 2010 to Nov 23, 2010.Source: From registration records (WHOIS / RDAP archive, who.is)
Jan 23, 2010Zone file: blogcn.com's nameservers moved from blogcndns.com to dns-diy.com between Jan 1, 2010 and Jan 23, 2010. Last seen at blogcndns.com: Jan 1, 2010 (registration record). First seen at dns-diy.com: Jan 23, 2010 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Feb 28, 2010Registrant: The registrant name or organization in the registration record changed; first recorded Feb 28, 2010. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Jul 11, 2010Registrant: The registrant name or organization in the registration record changed; first recorded Jul 11, 2010. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Aug 3, 2010Registrant: The registrant name or organization in the registration record changed; first recorded Aug 3, 2010. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Dec 24, 2010 – Mar 27, 2011Zone file: Registration records listed yo2wp.com nameservers (ns1.yo2wp.com) for blogcn.com from Dec 24, 2010 to Mar 27, 2011.Source: From registration records (WHOIS / RDAP archive, who.is)
Dec 24, 2010Zone file: blogcn.com's nameservers moved from dns-diy.com to yo2wp.com between Nov 23, 2010 and Dec 24, 2010. Last seen at dns-diy.com: Nov 23, 2010 (registration record). First seen at yo2wp.com: Dec 24, 2010 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Apr 15, 2011 – Oct 13, 2013Zone file: Registration records listed dns-diy.com nameservers (ns1.dns-diy.com) for blogcn.com from Apr 15, 2011 to Oct 13, 2013.Source: From registration records (WHOIS / RDAP archive, who.is)
Apr 15, 2011Zone file: blogcn.com's nameservers moved from yo2wp.com to dns-diy.com between Mar 27, 2011 and Apr 15, 2011. Last seen at yo2wp.com: Mar 27, 2011 (registration record). First seen at dns-diy.com: Apr 15, 2011 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Jun 7, 2011Registrant: The registrant name or organization in the registration record changed; first recorded Jun 7, 2011. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Jul 2, 2011 – Sep 21, 2012Registrar: Registrar 35 TECHNOLOGY CO., LTD in the WHOIS and RDAP records held for blogcn.com, from Jul 2, 2011 to Sep 21, 2012.Source: WHOIS / RDAP archive (who.is)
Nov 18, 2011Registrant: The registrant name or organization in the registration record changed; first recorded Nov 18, 2011. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Oct 18, 2013 – Apr 1, 2016Zone file: dns-diy.com (ns1.dns-diy.com, ns2.dns-diy.com, ns3.dns-diy.com…) were the nameservers listed for blogcn.com at every ICANN zone-file snapshot AboutUs holds from Oct 18, 2013 to Apr 1, 2016 (snapshots exist for only part of 2013–2018).Source: ICANN zone-file snapshots, 2013–2018 (legacy archive)
Jul 26, 2016 – Apr 5, 2024Registrar: Registrar Xiamen 35.Com Technology Co., Ltd (IANA 1316) in the WHOIS and RDAP records held for blogcn.com, from Jul 26, 2016 to Apr 5, 2024.Source: WHOIS / RDAP archive (who.is)
Jul 26, 2016Registrant: The registrant name or organization in the registration record changed; first recorded Jul 26, 2016. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Jul 26, 2016 – Apr 2, 2018Zone file: Registration records listed dnspod.net nameservers (f1g1ns1.dnspod.net, f1g1ns2.dnspod.net) for blogcn.com from Jul 26, 2016 to Apr 2, 2018. Days a zone file covers are shown from the zone file instead.Source: From registration records (WHOIS / RDAP archive, who.is)
Jul 26, 2016Zone file: blogcn.com's nameservers moved from dns-diy.com to dnspod.net at some point between Apr 1, 2016 and Jul 26, 2016. Last seen at dns-diy.com: Apr 1, 2016 (ICANN zone-file snapshot). First seen at dnspod.net: Jul 26, 2016 (registration record). AboutUs holds no nameserver records for the 4 months in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (ICANN zone-file snapshot → registration record)
Apr 3, 2018Zone file: dnspod.net (f1g1ns1.dnspod.net, f1g1ns2.dnspod.net) were the nameservers listed for blogcn.com at every ICANN zone-file snapshot AboutUs holds from Apr 3, 2018 to Apr 3, 2018 (snapshots exist for only part of 2013–2018).Source: ICANN zone-file snapshots, 2013–2018 (legacy archive)
Apr 4, 2018 – Oct 18, 2019Zone file: Registration records listed dnspod.net nameservers (f1g1ns1.dnspod.net, f1g1ns2.dnspod.net) for blogcn.com from Apr 4, 2018 to Oct 18, 2019. Days a zone file covers are shown from the zone file instead.Source: From registration records (WHOIS / RDAP archive, who.is)
Nov 24, 2019 – Jun 4, 2026Zone file: Registration records listed Cloudflare nameservers (greg.ns.cloudflare.com, zoe.ns.cloudflare.com) for blogcn.com from Nov 24, 2019 to Jun 4, 2026.Source: From registration records (WHOIS / RDAP archive, who.is)
Nov 24, 2019Zone file: blogcn.com's nameservers moved from dnspod.net to Cloudflare between Oct 18, 2019 and Nov 24, 2019. Last seen at dnspod.net: Oct 18, 2019 (registration record). First seen at Cloudflare: Nov 24, 2019 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Aug 14, 2024 – Oct 11, 2026Registrar: Registrar Xiamen 35.com Information Co., Ltd. (IANA 4163) in the registration data recorded, first on Aug 14, 2024 and most recently on Oct 11, 2026.Source: RDAP, fetched Nov 10, 2026
May 9, 2026 – Nov 19, 2026Certificate: Google Trust Services issued 3 certificates for blogcn.com from May 9, 2026, the latest valid until Jan 31, 2027. Seen in use on Oct 5, 2026.Source: Certificate Transparency logs (AboutUs's own certificate-log reader); TLS check, Oct 5, 2026
Jun 2, 2026 – Nov 19, 2026Certificate: Let's Encrypt issued 3 certificates for blogcn.com from Jun 2, 2026, the latest valid until Jan 6, 2027.Source: Certificate Transparency logs (AboutUs's own certificate-log reader)
Jun 23, 2026 – Nov 10, 2026AboutUs record: Authority and Safety last refreshed Nov 10, 2026.Source: AboutUs checks
Sep 8, 2026 – Nov 15, 2026Zone file: First seen in the .com zone file records AboutUs holds on Sep 8, 2026; latest sighting Nov 15, 2026. Nameservers on Nov 15, 2026: greg.ns.cloudflare.com, zoe.ns.cloudflare.com.Source: ICANN CZDS zone file, snapshot Nov 15, 2026
1 of 2 safety checks passed (Nov 19, 2026).
Registered 2002 · AboutUs could not get a response over HTTPS when it checked (Nov 19, 2026)
Make sure the site responds over HTTPS with a valid certificate.
AboutUs has not vetted this site. Everything below is what we could measure automatically. Anything you do on the site — paying, sharing personal details, downloading — is between you and the site, not AboutUs.
Current facts
Latest available measurements; dated entries retain their dates. These are measurements, not an endorsement of the site.
latest result
Domain registered Nov 22, 2002 — 23 years old.
latest result
Registrar on record: Xiamen 35.com Information Co., Ltd. — unchanged since AboutUs began tracking (Aug 29, 2026).
Authority 67/100— ahead of 67% of the August 2026 scored sampleClear
Why this authority score
67 is a percentile: higher than 67% of sites we score.
How it's calculated
Prominence (Tranco rank #112,212)+7
Verified continuity: 24.0 years (RDAP registration)+10
Security & email hygiene+4
Calibration adjustment (published map)+13
Model score: 34/99 — what these reason lines add up to.
Published Authority (percentile): 67/100 — this site's rank against the August 2026 scored sample. Public Authority is capped at 99.
Safety evidence
No unexpired threat-feed result; name-similarity check available (recorded about 8 days ago); 3/3 transport and email checks available (oldest recorded about 8 days ago). This is evidence coverage, not a probability that a website is safe.
Missing DMARC (mild)
Site history
Dated record — historical facts always carry their date.