telegramindex.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeSSL: 70 days left3 years old
40
telegramindex.com was registered on 22 Oct 2023 via Dynadot Inc and the registry expiry is 22 Oct 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/telegramindex.com.
telegramindex.com publishes 2 nameservers. DNSSEC is not signed.
telegramindex.com has 1 IPv4 address (162.4.84.215). The geolocation database places 162.4.84.215 in Los Angeles, United States.
The TLS certificate from YE1 is not valid (TLS 1.3).
No safety warning was recorded for telegramindex.com in the checks that ran.
Domain · RDAP/WHOIS
telegramindex.com was registered on 22 Oct 2023 via Dynadot Inc. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/telegramindex.com.
| Registered | since 22 Oct 2023 |
|---|---|
| Created | 22 October 2023 |
| Updated | 30 October 2026 |
| Expires | 22 October 2027 |
| Registrar | Dynadot Inc |
| Status | client transfer prohibited |
| Nameservers | ns1.parklogic.com, ns2.parklogic.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/telegramindex.com |
telegramindex.com carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.
Nameserver ns1.parklogic.com is published for telegramindex.com in the registration record from https://rdap.verisign.com/com/v1/domain/telegramindex.com.
Nameserver ns2.parklogic.com is published for telegramindex.com in the registration record from https://rdap.verisign.com/com/v1/domain/telegramindex.com.
DNS
telegramindex.com has 1 address record, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 162.4.84.215 |
|---|---|
| AAAA | — |
| NS | ns1.parklogic.com, ns2.parklogic.com |
| MX | mx156.hostedmxserver.com (10) |
| SPF | present |
| DMARC | absent |
| CAA | issue letsencrypt.org |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at telegramindex.com is "v=spf1 -all".
IPv4 address 162.4.84.215 answers for telegramindex.com at resolver 1.1.1.1:53.
Mail exchanger mx156.hostedmxserver.com has preference 10.
A random label under telegramindex.com also resolved, which means wildcard DNS is on.
A nameserver belongs to a parking host.
Hosting and geo
telegramindex.com is placed in Los Angeles, United States by the local geolocation database (db-ip).
| Address | 162.4.84.215 |
|---|---|
| Country | United States |
| City | Los Angeles |
| Source | db-ip |
SSL/TLS
The certificate for telegramindex.com is not valid, with 70 days left and 1 subject alternative name. Source: tls:443.
| Issuer | YE1 |
|---|---|
| Subject | telegramindex.com |
| Valid from | 12 October 2026 |
| Valid until | 10 January 2027 |
| Days left | 70 |
| SAN count | 1 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: telegramindex.com.
Validation result: certificate did not validate
Tech stack
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
On-page checks
The homepage fetch did not return a status code.
| Status | none |
|---|
Get "https://telegramindex.com/": tls: failed to verify certificate: x509: certificate signed by unknown authority
Security
Family DNS for telegramindex.com is clear, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | clear |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.
Score breakdown
Availability 10 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 0 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 10 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 0 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.
Safety lists 15 of 15. Points only when the checks ran and came back clean. Unknown is not clean.
Domain age 5 of 5. Five points at one year, two points at 30 days.
Change history
- October 2026: rdap nameservers changed from 5014.ns1.abovedomains.com,5014.ns2.abovedomains.com to ns1.parklogic.com,ns2.parklogic.com.
- October 2026: rdap updated changed from 2026-10-23T08:39:45Z to 2026-10-30T11:39:03Z.
- October 2026: dns a changed from 103.224.182.248 to 162.4.84.215.
- October 2026: dns caa changed from empty to issue letsencrypt.org.
- October 2026: dns mx changed from park-mx.above.com to mx156.hostedmxserver.com.
- October 2026: dns ns changed from ns1.abovedomains.com,ns2.abovedomains.com to ns1.parklogic.com,ns2.parklogic.com.
- October 2026: dns spf changed from v=spf1 ip6:fdcf:abda:4154::/48 -all to v=spf1 -all.
- October 2026: tls not_after changed from 2027-01-21T05:52:59Z to 2027-01-10T01:04:18Z.
- October 2026: tls valid changed from true to false.
- October 2026: http status_class changed from 2xx to empty.
- October 2026: tech removed Apache HTTP Server.
- October 2026: geo city changed from empty to Los Angeles.
- October 2026: geo country changed from empty to United States.
Questions
Is telegramindex.com safe?
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
Who hosts telegramindex.com?
telegramindex.com is placed in Los Angeles, United States.
When does telegramindex.com expire?
telegramindex.com expires on 22 October 2027 according to https://rdap.verisign.com/com/v1/domain/telegramindex.com.
Who owns telegramindex.com?
The registry did not return a person or a company for telegramindex.com. RDAP often redacts the registrant. The registrar on file is Dynadot Inc.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/telegramindex.com at 2026-10-30T14:16:07Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:16:07Z
- TLS source tls:443 at 2026-10-30T14:16:07Z
- HTTP source https://telegramindex.com/ at 2026-10-30T14:16:07Z
- Tech source not available at 2026-10-30T14:16:07Z
- Geo source db-ip at 2026-10-30T14:16:07Z
- Safety source family DNS and local lists at 2026-10-30T14:16:07Z
Related reports
No other indexable reports share this TLD, host, or registrar yet.
Owner of this site?
Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.
How to read this report
The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.