chatmehard.net
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineFamily DNS blocked7 years old
25
chatmehard.net was registered on 16 Oct 2019 via Mesh Digital Limited and the registry expiry is 16 Oct 2027. WHOIS data came from RDAP at https://rdap.verisign.com/net/v1/domain/chatmehard.net.
chatmehard.net publishes 2 nameservers. DNSSEC is not signed.
chatmehard.net has 1 IPv4 address (194.195.92.129). The geolocation database places 194.195.92.129 in Phoenix, United States.
Domain · RDAP/WHOIS
chatmehard.net was registered on 16 Oct 2019 via Mesh Digital Limited. The registry returned 3 status values and 2 nameservers from https://rdap.verisign.com/net/v1/domain/chatmehard.net.
| Registered | since 16 Oct 2019 |
|---|---|
| Created | 16 October 2019 |
| Updated | 23 October 2026 |
| Expires | 16 October 2027 |
| Registrar | Mesh Digital Limited |
| Status | client delete prohibited, client transfer prohibited, client update prohibited |
| Nameservers | gigi.ns.cloudflare.com, yoxall.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/net/v1/domain/chatmehard.net |
chatmehard.net carries the status "client delete prohibited". The registrar has asked the registry to refuse a delete. This is an EPP status on the domain object. It does not say the website is safe, and it does not name the person who registered it.
chatmehard.net 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.
chatmehard.net carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.
Nameserver gigi.ns.cloudflare.com is published for chatmehard.net in the registration record from https://rdap.verisign.com/net/v1/domain/chatmehard.net.
Nameserver yoxall.ns.cloudflare.com is published for chatmehard.net in the registration record from https://rdap.verisign.com/net/v1/domain/chatmehard.net.
DNS
chatmehard.net has 1 address record, 5 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 194.195.92.129 |
|---|---|
| AAAA | — |
| NS | gigi.ns.cloudflare.com, yoxall.ns.cloudflare.com |
| MX | aspmx.l.google.com (1) Google, alt1.aspmx.l.google.com (5) Google, alt2.aspmx.l.google.com (5) Google, alt3.aspmx.l.google.com (10) Google, alt4.aspmx.l.google.com (10) Google |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at chatmehard.net is "v=spf1 +a +mx ip4:185.111.89.208 ip4:66.111.4.224 include:spf.messagingengine.com ?all".
The DMARC text record at _dmarc.chatmehard.net is "v=DMARC1; p=none".
IPv4 address 194.195.92.129 answers for chatmehard.net at resolver 1.1.1.1:53.
Mail exchanger aspmx.l.google.com has preference 1. The host is recognised as Google.
Mail exchanger alt1.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt2.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt3.aspmx.l.google.com has preference 10. The host is recognised as Google.
Mail exchanger alt4.aspmx.l.google.com has preference 10. The host is recognised as Google.
Hosting and geo
chatmehard.net is placed in Phoenix, United States by the local geolocation database (db-ip).
| Address | 194.195.92.129 |
|---|---|
| Country | United States |
| City | Phoenix |
| Source | db-ip |
SSL/TLS
No TLS certificate was read for chatmehard.net on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
remote error: tls: internal error
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://chatmehard.net/": remote error: tls: internal error
Security
Family DNS for chatmehard.net is blocked, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | blocked |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Cloudflare family DNS returned a block for chatmehard.net. That resolver covers adult and malware names.
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 0 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: geo city changed from empty to Phoenix.
- October 2026: geo country changed from empty to United States.
Questions
Is chatmehard.net safe?
Cloudflare family DNS returned a block for chatmehard.net. That resolver covers adult and malware names.
Who hosts chatmehard.net?
chatmehard.net is placed in Phoenix, United States.
When does chatmehard.net expire?
chatmehard.net expires on 16 October 2027 according to https://rdap.verisign.com/net/v1/domain/chatmehard.net.
Who owns chatmehard.net?
The registry did not return a person or a company for chatmehard.net. RDAP often redacts the registrant. The registrar on file is Mesh Digital Limited.
Sources
- RDAP source https://rdap.verisign.com/net/v1/domain/chatmehard.net at 2026-10-30T14:51:18Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:51:18Z
- TLS source tls:443 at 2026-10-30T14:51:18Z
- HTTP source https://chatmehard.net/ at 2026-10-30T14:51:18Z
- Tech source not available at 2026-10-30T14:51:18Z
- Geo source db-ip at 2026-10-30T14:51:18Z
- Safety source family DNS and local lists at 2026-10-30T14:51:18Z
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.