Correct a description, link or other detail. Submissions are reviewed before publication.
Lifeline · telegram.me over time
Checked in the last 30 daysOlder, dated recordFrom registration records
On AboutUs since 2014 · 3 registrar changes since Aug 25, 2010 · 1 registrant change since 2010 · last checked Nov 20, 2026.
Registration
No registration date on file yet. AboutUs reads it from RDAP when the site is checked.
AboutUs record
AboutUs wiki pageJan 11, 2014An AboutUs wiki page described telegram.me from Jan 11, 2014 to Jan 11, 2014 (1 edit).Source: AboutUs wiki archive, 2006–2023Said about itself in 2014Jul 1, 2014“telegram.me is your first and best source for information about telegram. Here you will also find topics relating to issues of general interest. We hope you find what you are looking for!”Source: AboutUs wiki archive, 2014
Registrar
GoDaddy.com Inc R41-MEAug 25, 2010Registrar GoDaddy.com Inc R41-ME in the registration data recorded on Aug 25, 2010.Source: WHOIS / RDAP archive (who.is)Internet Capital, Inc. R172-ME (1510)Feb 24, 2014 – Oct 28, 2014Registrar Internet Capital, Inc. R172-ME (1510) in the WHOIS and RDAP records held for telegram.me, from Feb 24, 2014 to Oct 28, 2014.
Registrant
Registrant recordsAug 25, 2010 – Jun 25, 2026Registration records for telegram.me are held from Aug 25, 2010 to Jun 25, 2026 (122 records). 1 change of registrant name or organization is 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
No nameserver records held, Aug 2010 – Feb 2014No nameserver records held, Aug 2010 – Feb 2014No nameserver records held, Jul 2016 – May 2025No nameserver records held, Jul 2016 – May 2025Nameservers: GoDaddyAug 25, 2010Registration records listed GoDaddy nameservers (ns19.domaincontrol.com, ns20.domaincontrol.com) for telegram.me from Aug 25, 2010 to Aug 25, 2010.Source: From registration records (WHOIS / RDAP archive, who.is)
Certificate
GoDaddy.comGoDaddy.comNov 17, 2014 – Nov 22, 2026 (latest)GoDaddy.com issued 10 certificates for telegram.me from Nov 17, 2014, the latest valid until Apr 19, 2027. Seen in use on Nov 20, 2026.Source: Certificate Transparency logs (crt.sh + AboutUs's own certificate-log reader); TLS check, Nov 20, 2026
201520202025Apr ’26← last 12 months, drawn wider
Every dated fact on this lifeline (17)
Aug 25, 2010Registrar: Registrar GoDaddy.com Inc R41-ME in the registration data recorded on Aug 25, 2010.Source: WHOIS / RDAP archive (who.is)
Aug 25, 2010 – Jun 25, 2026Registrant: Registration records for telegram.me are held from Aug 25, 2010 to Jun 25, 2026 (122 records). 1 change of registrant name or organization is 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
Aug 25, 2010Zone file: Registration records listed GoDaddy nameservers (ns19.domaincontrol.com, ns20.domaincontrol.com) for telegram.me from Aug 25, 2010 to Aug 25, 2010.Source: From registration records (WHOIS / RDAP archive, who.is)
Jan 11, 2014AboutUs record: An AboutUs wiki page described telegram.me from Jan 11, 2014 to Jan 11, 2014 (1 edit).Source: AboutUs wiki archive, 2006–2023
Feb 24, 2014 – Oct 28, 2014Registrar: Registrar Internet Capital, Inc. R172-ME (1510) in the WHOIS and RDAP records held for telegram.me, from Feb 24, 2014 to Oct 28, 2014.Source: WHOIS / RDAP archive (who.is)
Current AboutUs record
Jul 18, 2026 – Nov 15, 2026 (latest)
Authority and Safety last refreshed Nov 15, 2026.
Source: AboutUs checks
Source: WHOIS / RDAP archive (who.is)
GoDaddy.com, LLC R41-ME (146)Nov 19, 2014 – Jul 11, 2016Registrar GoDaddy.com, LLC R41-ME (146) in the WHOIS and RDAP records held for telegram.me, from Nov 19, 2014 to Jul 11, 2016.Source: WHOIS / RDAP archive (who.is)
GoDaddy.com, LLCMay 2, 2025 – Jun 25, 2026 (latest)Registrar GoDaddy.com, LLC (IANA 146) in the WHOIS and RDAP records held for telegram.me, from May 2, 2025 to Jun 25, 2026.Source: WHOIS / RDAP archive (who.is)
Registrant change
Oct 28, 2014
The registrant name or organization in the registration record changed; first recorded Oct 28, 2014. 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
1 registrant change, 2010–2026
Nameservers: sedoparking.comFeb 24, 2014 – Oct 28, 2014Registration records listed sedoparking.com nameservers (ns1.sedoparking.com, ns2.sedoparking.com) for telegram.me from Feb 24, 2014 to Oct 28, 2014.Source: From registration records (WHOIS / RDAP archive, who.is)
DNS moved to sedoparking.comFeb 24, 2014telegram.me's nameservers moved from GoDaddy to sedoparking.com at some point between Aug 25, 2010 and Feb 24, 2014. Last seen at GoDaddy: Aug 25, 2010 (registration record). First seen at sedoparking.com: Feb 24, 2014 (registration record). AboutUs holds no nameserver records for the about 4 years in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Nameservers: GoDaddyNov 19, 2014 – Jul 11, 2016Registration records listed GoDaddy nameservers (pdns05.domaincontrol.com, pdns06.domaincontrol.com) for telegram.me from Nov 19, 2014 to Jul 11, 2016.Source: From registration records (WHOIS / RDAP archive, who.is)
DNS moved to GoDaddyNov 19, 2014telegram.me's nameservers moved from sedoparking.com to GoDaddy between Oct 28, 2014 and Nov 19, 2014. Last seen at sedoparking.com: Oct 28, 2014 (registration record). First seen at GoDaddy: Nov 19, 2014 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Nameservers: Google DomainsMay 2, 2025 – Jun 25, 2026Registration records listed Google Domains nameservers (ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com…) for telegram.me from May 2, 2025 to Jun 25, 2026.Source: From registration records (WHOIS / RDAP archive, who.is)
DNS moved to Google DomainsMay 2, 2025telegram.me's nameservers moved from GoDaddy to Google Domains at some point between Jul 11, 2016 and May 2, 2025. Last seen at GoDaddy: Jul 11, 2016 (registration record). First seen at Google Domains: May 2, 2025 (registration record). AboutUs holds no nameserver records for the about 9 years in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Feb 24, 2014 – Oct 28, 2014
Zone file: Registration records listed sedoparking.com nameservers (ns1.sedoparking.com, ns2.sedoparking.com) for telegram.me from Feb 24, 2014 to Oct 28, 2014.Source: From registration records (WHOIS / RDAP archive, who.is)
Feb 24, 2014Zone file: telegram.me's nameservers moved from GoDaddy to sedoparking.com at some point between Aug 25, 2010 and Feb 24, 2014. Last seen at GoDaddy: Aug 25, 2010 (registration record). First seen at sedoparking.com: Feb 24, 2014 (registration record). AboutUs holds no nameserver records for the about 4 years in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Jul 1, 2014AboutUs record: “telegram.me is your first and best source for information about telegram. Here you will also find topics relating to issues of general interest. We hope you find what you are looking for!”Source: AboutUs wiki archive, 2014
Oct 28, 2014Registrant: The registrant name or organization in the registration record changed; first recorded Oct 28, 2014. 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
Nov 17, 2014 – Nov 22, 2026Certificate: GoDaddy.com issued 10 certificates for telegram.me from Nov 17, 2014, the latest valid until Apr 19, 2027. Seen in use on Nov 20, 2026.Source: Certificate Transparency logs (crt.sh + AboutUs's own certificate-log reader); TLS check, Nov 20, 2026
Nov 19, 2014 – Jul 11, 2016Registrar: Registrar GoDaddy.com, LLC R41-ME (146) in the WHOIS and RDAP records held for telegram.me, from Nov 19, 2014 to Jul 11, 2016.Source: WHOIS / RDAP archive (who.is)
Nov 19, 2014 – Jul 11, 2016Zone file: Registration records listed GoDaddy nameservers (pdns05.domaincontrol.com, pdns06.domaincontrol.com) for telegram.me from Nov 19, 2014 to Jul 11, 2016.Source: From registration records (WHOIS / RDAP archive, who.is)
Nov 19, 2014Zone file: telegram.me's nameservers moved from sedoparking.com to GoDaddy between Oct 28, 2014 and Nov 19, 2014. Last seen at sedoparking.com: Oct 28, 2014 (registration record). First seen at GoDaddy: Nov 19, 2014 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)
May 2, 2025 – Jun 25, 2026Registrar: Registrar GoDaddy.com, LLC (IANA 146) in the WHOIS and RDAP records held for telegram.me, from May 2, 2025 to Jun 25, 2026.Source: WHOIS / RDAP archive (who.is)
May 2, 2025 – Jun 25, 2026Zone file: Registration records listed Google Domains nameservers (ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com…) for telegram.me from May 2, 2025 to Jun 25, 2026.Source: From registration records (WHOIS / RDAP archive, who.is)
May 2, 2025Zone file: telegram.me's nameservers moved from GoDaddy to Google Domains at some point between Jul 11, 2016 and May 2, 2025. Last seen at GoDaddy: Jul 11, 2016 (registration record). First seen at Google Domains: May 2, 2025 (registration record). AboutUs holds no nameserver records for the about 9 years in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Jul 18, 2026 – Nov 15, 2026AboutUs record: Authority and Safety last refreshed Nov 15, 2026.Source: AboutUs checks
Its address redirects to telegram.org, which answered over HTTPS
telegram.me has an AboutUs profile for public website intelligence, ownership context, trust signals, monitoring, and owner verification.
We withhold an authority number until independent evidence (global rank, link-graph presence) has accrued. The facts we do have about this site are shown below — we'd rather say “not enough signals yet” than invent a low score.
Safety evidence
Retained threat-feed result (recorded about 21 days ago); name-similarity check available (recorded about 7 days ago); 3/3 transport and email checks available (oldest recorded about 7 days ago). This is evidence coverage, not a probability that a website is safe.
No caution flags in the available scoring observations; this is not a complete safety assessment
What telegram.me said about itself, 2014
Quoted from the site's AboutUs wiki page in each year it changed (1 version). These are the page's own words at the time, not AboutUs's assessment. New words · dropped words
2014
telegram.me is your first and best source for information about telegram. Here you will also find topics relating to issues of general interest. We hope you find what you are looking for!
Site history
Dated record — historical facts always carry their date.