AboutUs hasn't finished checking this site yet — the live checks below are current; more details appear as we crawl it.
tel.com
Verifying against the live site and live WHOIS/DNS…
Common questions
Is tel.com legit or a scam?
tel.com was registered Aug 17, 1993 (33 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 tel.com?
Nobody has completed AboutUs's owner verification for tel.com. That's true of most sites here — it isn't itself a warning sign.
When was tel.com registered?
tel.com's registration dates to Aug 17, 1993 (33 years old), per public registration records. 1API GmbH is the registrar on record today.
Correct a description, link or other detail. Submissions are reviewed before publication.
Lifeline · tel.com over time
Checked in the last 30 daysOlder, dated recordFrom registration records
Registered 33 years ago · on AboutUs since 2013 · 1 registrar change since Aug 15, 2011 · no ownership change on record since 2007 · last checked Oct 30, 2026.
Registration
RegisteredAug 17, 1993tel.com was registered on Aug 17, 1993.Source: RDAP, fetched Oct 5, 2026
AboutUs record
AboutUs wiki pageNov 7, 2013An AboutUs wiki page described tel.com from Nov 7, 2013 to Nov 7, 2013 (1 edit).Source: AboutUs wiki archive, 2006–2023Current AboutUs recordJul 8, 2026 – Oct 5, 2026 (latest)Authority and Safety last refreshed Oct 5, 2026.
Registrar
PSI-Japan Inc.Aug 15, 2011 – Jul 11, 2014Registrar PSI-Japan Inc. (IANA 78) in the WHOIS and RDAP records held for tel.com, from Aug 15, 2011 to Jul 11, 2014.Source: WHOIS / RDAP archive (who.is)1API GmbH
Ownership
Ownership recordsMay 13, 2007 – Jun 20, 2026Registration records for tel.com are held from May 13, 2007 to Jun 20, 2026 (702 records). None shows a change of registrant. Privacy-service and redaction changes are not counted.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
No ownership changes recorded, 2007–2026
Zone file
Nameservers: iprevolution.co.jp, tel.comAug 15, 2011 – Apr 7, 2012Registration records listed iprevolution.co.jp, tel.com nameservers (ns2.iprevolution.co.jp, sbns2.tel.com) for tel.com from Aug 15, 2011 to Apr 7, 2012.Source: From registration records (WHOIS / RDAP archive, who.is)
Certificate
DigiCert IncDigiCert IncAug 18, 2025 – Oct 31, 2026DigiCert Inc issued 35 certificates for tel.com from Aug 18, 2025, the latest valid until May 14, 2027.Source: Certificate Transparency logs (AboutUs's own certificate-log reader)Network Solutions L.L.C.
200020102020Jan ’26Oct ’26← last 12 months, drawn wider
Every dated fact on this lifeline (25)
Aug 17, 1993Registration: tel.com was registered on Aug 17, 1993.Source: RDAP, fetched Oct 5, 2026
May 13, 2007 – Jun 20, 2026Ownership: Registration records for tel.com are held from May 13, 2007 to Jun 20, 2026 (702 records). None shows a change of registrant. Privacy-service and redaction changes are not counted.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Aug 15, 2011 – Jul 11, 2014Registrar: Registrar PSI-Japan Inc. (IANA 78) in the WHOIS and RDAP records held for tel.com, from Aug 15, 2011 to Jul 11, 2014.Source: WHOIS / RDAP archive (who.is)
Aug 15, 2011 – Apr 7, 2012Zone file: Registration records listed iprevolution.co.jp, tel.com nameservers (ns2.iprevolution.co.jp, sbns2.tel.com) for tel.com from Aug 15, 2011 to Apr 7, 2012.Source: From registration records (WHOIS / RDAP archive, who.is)
May 20, 2012 – Sep 13, 2012Zone file: Registration records listed iprevolution.co.jp nameservers (ns2.iprevolution.co.jp) for tel.com from May 20, 2012 to Sep 13, 2012.Source: From registration records (WHOIS / RDAP archive, who.is)
May 20, 2012
Source: AboutUs checks
1API GmbH
Jun 30, 2016 – Jul 31, 2026 (latest)
Registrar 1API GmbH (IANA 1387) in the registration data recorded, first on Jun 30, 2016 and most recently on Jul 31, 2026.
Source: RDAP, fetched Oct 5, 2026
Nameservers: iprevolution.co.jp
May 20, 2012 – Sep 13, 2012
Registration records listed iprevolution.co.jp nameservers (ns2.iprevolution.co.jp) for tel.com from May 20, 2012 to Sep 13, 2012.
Source: From registration records (WHOIS / RDAP archive, who.is)
DNS moved to iprevolution.co.jpMay 20, 2012tel.com's nameservers moved from iprevolution.co.jp, tel.com to iprevolution.co.jp between Apr 7, 2012 and May 20, 2012. Last seen at iprevolution.co.jp, tel.com: Apr 7, 2012 (registration record). First seen at iprevolution.co.jp: May 20, 2012 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Nameservers: iprevolution.co.jp, tel.comSep 17, 2012 – Oct 17, 2013Registration records listed iprevolution.co.jp, tel.com nameservers (ns2.iprevolution.co.jp, sbns2.tel.com) for tel.com from Sep 17, 2012 to Oct 17, 2013. Days a zone file covers are shown from the zone file instead.Source: From registration records (WHOIS / RDAP archive, who.is)
DNS moved to iprevolution.co.jp, tel.comSep 17, 2012tel.com's nameservers moved from iprevolution.co.jp to iprevolution.co.jp, tel.com between Sep 13, 2012 and Sep 17, 2012. Last seen at iprevolution.co.jp: Sep 13, 2012 (registration record). First seen at iprevolution.co.jp, tel.com: Sep 17, 2012 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Nameservers: iprevolution.co.jp, tel.comOct 18, 2013 – Apr 1, 2016iprevolution.co.jp, tel.com (ns2.iprevolution.co.jp, sbns2.tel.com) were the nameservers listed for tel.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: iprevolution.co.jp, tel.comApr 2, 2016 – Jul 19, 2016Registration records listed iprevolution.co.jp, tel.com nameservers (ns2.iprevolution.co.jp, sbns2.tel.com) for tel.com from Apr 2, 2016 to Jul 19, 2016. Days a zone file covers are shown from the zone file instead.Source: From registration records (WHOIS / RDAP archive, who.is)
Nameservers: tel.com, vips.ne.jpAug 29, 2016 – Apr 2, 2018Registration records listed tel.com, vips.ne.jp nameservers (ns00.vips.ne.jp, ns01.vips.ne.jp, sbns1.tel.com) for tel.com from Aug 29, 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 tel.com, vips.ne.jpAug 29, 2016tel.com's nameservers moved from iprevolution.co.jp, tel.com to tel.com, vips.ne.jp between Jul 19, 2016 and Aug 29, 2016. Last seen at iprevolution.co.jp, tel.com: Jul 19, 2016 (registration record). First seen at tel.com, vips.ne.jp: Aug 29, 2016 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Nameservers: tel.com, vips.ne.jpApr 3, 2018tel.com, vips.ne.jp (ns00.vips.ne.jp, ns01.vips.ne.jp, sbns1.tel.com) were the nameservers listed for tel.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: tel.com, vips.ne.jpNameservers: tel.com, vips.ne.jpApr 4, 2018 – Jun 20, 2026Registration records listed tel.com, vips.ne.jp nameservers (ns00.vips.ne.jp, ns01.vips.ne.jp, sbns1.tel.com) for tel.com from Apr 4, 2018 to Jun 20, 2026. Days a zone file covers are shown from the zone file instead.Source: From registration records (WHOIS / RDAP archive, who.is)
Seen in the .com zone fileSep 8, 2026 – Oct 30, 2026 (latest)First seen in the .com zone file records AboutUs holds on Sep 8, 2026; latest sighting Oct 30, 2026. Nameservers on Oct 30, 2026: ns00.vips.ne.jp, ns01.vips.ne.jp, sbns1.tel.com.Source: ICANN CZDS zone file, snapshot Oct 30, 2026
Network Solutions L.L.C.
Sep 16, 2025 – Oct 31, 2026
Network Solutions L.L.C. issued 4 certificates for tel.com from Sep 16, 2025, the latest valid until Dec 16, 2026.
Source: Certificate Transparency logs (AboutUs's own certificate-log reader)
Network SolutionsNetwork SolutionsNov 10, 2025 – Oct 25, 2026Network Solutions issued 2 certificates for tel.com from Nov 10, 2025, the latest valid until Oct 25, 2026.Source: Certificate Transparency logs (AboutUs's own certificate-log reader)
Sectigo LimitedApr 13, 2026 – Oct 31, 2026Sectigo Limited issued 2 certificates for tel.com from Apr 13, 2026, the latest valid until Apr 13, 2027.Source: Certificate Transparency logs (AboutUs's own certificate-log reader)
AmazonApr 15, 2026 – Oct 31, 2026Amazon issued 5 certificates for tel.com from Apr 15, 2026, the latest valid until Apr 15, 2027.Source: Certificate Transparency logs (AboutUs's own certificate-log reader)
SECOM Trust Systems Co.Jul 28, 2026 – Oct 31, 2026SECOM Trust Systems Co. issued 5 certificates for tel.com from Jul 28, 2026, the latest valid until Apr 27, 2027.Source: Certificate Transparency logs (AboutUs's own certificate-log reader)
NijimoAug 18, 2026 – Oct 31, 2026Nijimo issued 2 certificates for tel.com from Aug 18, 2026, the latest valid until Mar 4, 2027.Source: Certificate Transparency logs (AboutUs's own certificate-log reader)
Zone file: tel.com's nameservers moved from iprevolution.co.jp, tel.com to iprevolution.co.jp between Apr 7, 2012 and May 20, 2012. Last seen at iprevolution.co.jp, tel.com: Apr 7, 2012 (registration record). First seen at iprevolution.co.jp: May 20, 2012 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Sep 17, 2012 – Oct 17, 2013Zone file: Registration records listed iprevolution.co.jp, tel.com nameservers (ns2.iprevolution.co.jp, sbns2.tel.com) for tel.com from Sep 17, 2012 to Oct 17, 2013. Days a zone file covers are shown from the zone file instead.Source: From registration records (WHOIS / RDAP archive, who.is)
Sep 17, 2012Zone file: tel.com's nameservers moved from iprevolution.co.jp to iprevolution.co.jp, tel.com between Sep 13, 2012 and Sep 17, 2012. Last seen at iprevolution.co.jp: Sep 13, 2012 (registration record). First seen at iprevolution.co.jp, tel.com: Sep 17, 2012 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Oct 18, 2013 – Apr 1, 2016Zone file: iprevolution.co.jp, tel.com (ns2.iprevolution.co.jp, sbns2.tel.com) were the nameservers listed for tel.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)
Nov 7, 2013AboutUs record: An AboutUs wiki page described tel.com from Nov 7, 2013 to Nov 7, 2013 (1 edit).Source: AboutUs wiki archive, 2006–2023
Apr 2, 2016 – Jul 19, 2016Zone file: Registration records listed iprevolution.co.jp, tel.com nameservers (ns2.iprevolution.co.jp, sbns2.tel.com) for tel.com from Apr 2, 2016 to Jul 19, 2016. Days a zone file covers are shown from the zone file instead.Source: From registration records (WHOIS / RDAP archive, who.is)
Jun 30, 2016 – Jul 31, 2026Registrar: Registrar 1API GmbH (IANA 1387) in the registration data recorded, first on Jun 30, 2016 and most recently on Jul 31, 2026.Source: RDAP, fetched Oct 5, 2026
Aug 29, 2016 – Apr 2, 2018Zone file: Registration records listed tel.com, vips.ne.jp nameservers (ns00.vips.ne.jp, ns01.vips.ne.jp, sbns1.tel.com) for tel.com from Aug 29, 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)
Aug 29, 2016Zone file: tel.com's nameservers moved from iprevolution.co.jp, tel.com to tel.com, vips.ne.jp between Jul 19, 2016 and Aug 29, 2016. Last seen at iprevolution.co.jp, tel.com: Jul 19, 2016 (registration record). First seen at tel.com, vips.ne.jp: Aug 29, 2016 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Apr 3, 2018Zone file: tel.com, vips.ne.jp (ns00.vips.ne.jp, ns01.vips.ne.jp, sbns1.tel.com) were the nameservers listed for tel.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 – Jun 20, 2026Zone file: Registration records listed tel.com, vips.ne.jp nameservers (ns00.vips.ne.jp, ns01.vips.ne.jp, sbns1.tel.com) for tel.com from Apr 4, 2018 to Jun 20, 2026. Days a zone file covers are shown from the zone file instead.Source: From registration records (WHOIS / RDAP archive, who.is)
Aug 18, 2025 – Oct 31, 2026Certificate: DigiCert Inc issued 35 certificates for tel.com from Aug 18, 2025, the latest valid until May 14, 2027.Source: Certificate Transparency logs (AboutUs's own certificate-log reader)
Sep 16, 2025 – Oct 31, 2026Certificate: Network Solutions L.L.C. issued 4 certificates for tel.com from Sep 16, 2025, the latest valid until Dec 16, 2026.Source: Certificate Transparency logs (AboutUs's own certificate-log reader)
Nov 10, 2025 – Oct 25, 2026Certificate: Network Solutions issued 2 certificates for tel.com from Nov 10, 2025, the latest valid until Oct 25, 2026.Source: Certificate Transparency logs (AboutUs's own certificate-log reader)
Apr 13, 2026 – Oct 31, 2026Certificate: Sectigo Limited issued 2 certificates for tel.com from Apr 13, 2026, the latest valid until Apr 13, 2027.Source: Certificate Transparency logs (AboutUs's own certificate-log reader)
Apr 15, 2026 – Oct 31, 2026Certificate: Amazon issued 5 certificates for tel.com from Apr 15, 2026, the latest valid until Apr 15, 2027.Source: Certificate Transparency logs (AboutUs's own certificate-log reader)
Jul 8, 2026 – Oct 5, 2026AboutUs record: Authority and Safety last refreshed Oct 5, 2026.Source: AboutUs checks
Jul 28, 2026 – Oct 31, 2026Certificate: SECOM Trust Systems Co. issued 5 certificates for tel.com from Jul 28, 2026, the latest valid until Apr 27, 2027.Source: Certificate Transparency logs (AboutUs's own certificate-log reader)
Aug 18, 2026 – Oct 31, 2026Certificate: Nijimo issued 2 certificates for tel.com from Aug 18, 2026, the latest valid until Mar 4, 2027.Source: Certificate Transparency logs (AboutUs's own certificate-log reader)
Sep 8, 2026 – Oct 30, 2026Zone file: First seen in the .com zone file records AboutUs holds on Sep 8, 2026; latest sighting Oct 30, 2026. Nameservers on Oct 30, 2026: ns00.vips.ne.jp, ns01.vips.ne.jp, sbns1.tel.com.Source: ICANN CZDS zone file, snapshot Oct 30, 2026
0 of 2 safety checks passed (Oct 31, 2026).
Registered 1993 · AboutUs could not get a response over HTTPS when it checked (Oct 31, 2026)
tel.com has an AboutUs profile for public website intelligence, ownership context, trust signals, monitoring, and owner verification.
Add a public A or AAAA record so the domain resolves.
HTTPS (failed)
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 Aug 17, 1993 — 33 years old.
latest result
Registrar on record: 1API GmbH — unchanged since AboutUs began tracking (Jul 31, 2026).
Authority 55/100— ahead of 55% of the August 2026 scored sampleClear
Why this authority score
55 is a percentile: higher than 55% of sites we score.
How it's calculated
Prominence (Tranco rank #204,917)+6
Verified continuity: 33.2 years (RDAP registration)+11
Security & email hygiene+3
Calibration adjustment (published map)+9
Model score: 29/99 — what these reason lines add up to.
Published Authority (percentile): 55/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 25 days ago); 3/3 transport and email checks available (oldest recorded about 25 days ago). This is evidence coverage, not a probability that a website is safe.
Recorded HTTPS check did not confirm a valid connection
Site history
Dated record — historical facts always carry their date.