dalechatea.me
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 31 days left11 years oldTranco #71724
85
dalechatea.me was registered on 5 Jul 2015 via Soluciones Corporativas IP, SL and the registry expiry is 5 Jul 2029. WHOIS data came from RDAP at https://rdap.identitydigital.services/rdap/domain/dalechatea.me.
dalechatea.me publishes 2 nameservers. DNSSEC is signed.
dalechatea.me has 3 IPv4 addresses (104.26.14.97, 104.26.15.97, 172.67.75.153) and 3 IPv6 addresses (2606:4700:20::681a:e61, 2606:4700:20::681a:f61, 2606:4700:20::ac43:4b99). The geolocation database places 104.26.14.97 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 31 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, Cloudflare Browser Insights, Google Analytics and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for dalechatea.me in the checks that ran.
Domain · RDAP/WHOIS
dalechatea.me was registered on 5 Jul 2015 via Soluciones Corporativas IP, SL. The registry returned 1 status value and 2 nameservers from https://rdap.identitydigital.services/rdap/domain/dalechatea.me.
| Registered | since 5 Jul 2015 |
|---|---|
| Created | 5 July 2015 |
| Updated | 12 August 2026 |
| Expires | 5 July 2029 |
| Registrar | Soluciones Corporativas IP, SL |
| Status | client transfer prohibited |
| Nameservers | seth.ns.cloudflare.com, coco.ns.cloudflare.com |
| DNSSEC | yes |
| Source | https://rdap.identitydigital.services/rdap/domain/dalechatea.me |
dalechatea.me 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 seth.ns.cloudflare.com is published for dalechatea.me in the registration record from https://rdap.identitydigital.services/rdap/domain/dalechatea.me.
Nameserver coco.ns.cloudflare.com is published for dalechatea.me in the registration record from https://rdap.identitydigital.services/rdap/domain/dalechatea.me.
DNS
dalechatea.me has 6 address records, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.26.14.97, 104.26.15.97, 172.67.75.153 |
|---|---|
| AAAA | 2606:4700:20::681a:e61, 2606:4700:20::681a:f61, 2606:4700:20::ac43:4b99 |
| NS | coco.ns.cloudflare.com, seth.ns.cloudflare.com |
| MX | mail.dalechatea.me (10) |
| SPF | present |
| DMARC | present |
| CAA | issue comodoca.com, issue digicert.com; cansignhttpexchanges=yes, issue letsencrypt.org, issue pki.goog; cansignhttpexchanges=yes, issue ssl.com, issuewild comodoca.com, issuewild digicert.com; cansignhttpexchanges=yes, issuewild letsencrypt.org, issuewild pki.goog; cansignhttpexchanges=yes, issuewild ssl.com |
| Wildcard | off |
| DNSSEC | signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at dalechatea.me is "v=spf1 +mx +a +ip4:148.113.218.14 ~all".
The DMARC text record at _dmarc.dalechatea.me is "v=DMARC1; p=quarantine; rua=mailto:[email protected]".
IPv4 address 104.26.14.97 answers for dalechatea.me at resolver 1.1.1.1:53.
IPv4 address 104.26.15.97 answers for dalechatea.me at resolver 1.1.1.1:53.
IPv4 address 172.67.75.153 answers for dalechatea.me at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::681a:e61 answers for dalechatea.me at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::681a:f61 answers for dalechatea.me at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::ac43:4b99 answers for dalechatea.me at resolver 1.1.1.1:53.
Mail exchanger mail.dalechatea.me has preference 10.
Hosting and geo
dalechatea.me is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.26.14.97 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for dalechatea.me is valid, with 31 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | dalechatea.me |
| Valid from | 2 September 2026 |
| Valid until | 1 December 2026 |
| Days left | 31 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.dalechatea.me, dalechatea.me.
Tech stack
Tech detection checked the fetched homepage and named 4 products. Source: wappalyzergo.
- Cloudflare · CDN
- Cloudflare Browser Insights · Analytics, RUM
- Google Analytics · Analytics
- HTTP/3 · Miscellaneous
Cloudflare is filed under CDN.
Cloudflare Browser Insights is filed under Analytics, RUM.
Google Analytics is filed under Analytics.
HTTP/3 is filed under Miscellaneous.
On-page checks
The homepage returned HTTP 200 in 323 ms. The target title is 46 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 323 ms |
| Title length | 46 yes |
| Quoted title | "Dale Chat - Chat online, gratis y sin registro" |
| Meta description | "Chatea gratis en Dale Chat, chat online para hacer amigos y chatear sin registro y gratis. Estás en el sitio oficial de Dale Chat en dalechatea.me." yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | index,all |
| Canonical | https://dalechatea.me |
| Language | es |
| Links | 37 |
| Images | 13 |
| Favicon | yes |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Security
Family DNS for dalechatea.me 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 25 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 20 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 20 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 created changed from 2015-07-05T22:02:09Z to 2015-07-05T22:02:09.239Z.
- October 2026: rdap dnssec changed from unknown to yes.
- October 2026: rdap expires changed from 2029-07-05T22:02:09Z to 2029-07-05T22:02:09.239Z.
- October 2026: rdap statuses changed from clienttransferprohibited to client transfer prohibited.
- October 2026: rdap updated changed from 2026-08-12T08:15:26Z to 2026-08-12T08:15:26.433Z.
Questions
Is dalechatea.me 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 dalechatea.me?
dalechatea.me is placed in Toronto, Canada.
When does dalechatea.me expire?
dalechatea.me expires on 5 July 2029 according to https://rdap.identitydigital.services/rdap/domain/dalechatea.me.
Who owns dalechatea.me?
The registry did not return a person or a company for dalechatea.me. RDAP often redacts the registrant. The registrar on file is Soluciones Corporativas IP, SL.
Sources
- RDAP source https://rdap.identitydigital.services/rdap/domain/dalechatea.me at 2026-10-30T14:43:46Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:43:46Z
- TLS source tls:443 at 2026-10-30T14:43:46Z
- HTTP source https://dalechatea.me/ at 2026-10-30T14:43:46Z
- Tech source wappalyzergo at 2026-10-30T14:43:46Z
- Geo source db-ip at 2026-10-30T14:43:46Z
- Safety source family DNS and local lists at 2026-10-30T14:43:46Z
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.