baxan.chat
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 83 days left4 years old
65
baxan.chat was registered on 28 Dec 2021 via Name.com, Inc. and the registry expiry is 28 Dec 2026. WHOIS data came from RDAP at https://rdap.identitydigital.services/rdap/domain/baxan.chat.
baxan.chat publishes 2 nameservers. DNSSEC is not signed.
baxan.chat has 2 IPv4 addresses (104.21.63.94, 172.67.145.29) and 2 IPv6 addresses (2606:4700:3032::6815:3f5e, 2606:4700:3035::ac43:911d). The geolocation database places 104.21.63.94 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 83 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, HTTP/3, Microsoft ASP.NET and Plesk. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for baxan.chat in the checks that ran.
Domain · RDAP/WHOIS
baxan.chat was registered on 28 Dec 2021 via Name.com, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.identitydigital.services/rdap/domain/baxan.chat.
| Registered | since 28 Dec 2021 |
|---|---|
| Created | 28 December 2021 |
| Updated | 11 August 2026 |
| Expires | 28 December 2026 |
| Registrar | Name.com, Inc. |
| Status | client transfer prohibited |
| Nameservers | dara.ns.cloudflare.com, bill.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.identitydigital.services/rdap/domain/baxan.chat |
baxan.chat 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 dara.ns.cloudflare.com is published for baxan.chat in the registration record from https://rdap.identitydigital.services/rdap/domain/baxan.chat.
Nameserver bill.ns.cloudflare.com is published for baxan.chat in the registration record from https://rdap.identitydigital.services/rdap/domain/baxan.chat.
DNS
baxan.chat has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.63.94, 172.67.145.29 |
|---|---|
| AAAA | 2606:4700:3032::6815:3f5e, 2606:4700:3035::ac43:911d |
| NS | bill.ns.cloudflare.com, dara.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.21.63.94 answers for baxan.chat at resolver 1.1.1.1:53.
IPv4 address 172.67.145.29 answers for baxan.chat at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3032::6815:3f5e answers for baxan.chat at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3035::ac43:911d answers for baxan.chat at resolver 1.1.1.1:53.
Hosting and geo
baxan.chat is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.63.94 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for baxan.chat is valid, with 83 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | baxan.chat |
| Valid from | 24 October 2026 |
| Valid until | 22 January 2027 |
| Days left | 83 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.baxan.chat, baxan.chat.
Tech stack
Tech detection checked the fetched homepage and named 4 products. Source: wappalyzergo.
- Cloudflare · CDN
- HTTP/3 · Miscellaneous
- Microsoft ASP.NET · Web frameworks
- Plesk · Hosting panels
Cloudflare is filed under CDN.
HTTP/3 is filed under Miscellaneous.
Microsoft ASP.NET is filed under Web frameworks.
Plesk is filed under Hosting panels.
On-page checks
The homepage returned HTTP 200 in 267 ms. The target title is 9 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 267 ms |
| Title length | 9 yes |
| Quoted title | "Kurdstage" |
| Meta description | none no |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | en |
| Links | 0 |
| Images | 0 |
| Favicon | no |
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 baxan.chat 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 0 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
First checked on 30 October 2026; changes will appear here.
Questions
Is baxan.chat 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 baxan.chat?
baxan.chat is placed in Toronto, Canada.
When does baxan.chat expire?
baxan.chat expires on 28 December 2026 according to https://rdap.identitydigital.services/rdap/domain/baxan.chat.
Who owns baxan.chat?
The registry did not return a person or a company for baxan.chat. RDAP often redacts the registrant. The registrar on file is Name.com, Inc..
Sources
- RDAP source https://rdap.identitydigital.services/rdap/domain/baxan.chat at 2026-10-30T13:36:25Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:36:25Z
- TLS source tls:443 at 2026-10-30T13:36:25Z
- HTTP source https://baxan.chat/ at 2026-10-30T13:36:25Z
- Tech source wappalyzergo at 2026-10-30T13:36:25Z
- Geo source db-ip at 2026-10-30T13:36:25Z
- Safety source family DNS and local lists at 2026-10-30T13:36:25Z
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.