gazo-chat.net
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
60
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
60
gazo-chat.net was registered on 7 Jul 2011 via GMO Internet Group, Inc. d/b/a Onamae.com and the registry expiry is 7 Jul 2027. WHOIS data came from RDAP at https://rdap.verisign.com/net/v1/domain/gazo-chat.net.
gazo-chat.net publishes 2 nameservers. DNSSEC is not signed.
gazo-chat.net has 1 IPv4 address (172.104.64.123). The geolocation database places 172.104.64.123 in Shibuya City, Japan.
The TLS certificate from YR2 is valid and has 36 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Bootstrap, Google Analytics, Google Hosted Libraries, LiteSpeed, i-mobile and jQuery. The fingerprints ran on the homepage that was already downloaded.
gazo-chat.net was registered on 7 Jul 2011 via GMO Internet Group, Inc. d/b/a Onamae.com. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/net/v1/domain/gazo-chat.net.
| Registered | since 7 Jul 2011 |
|---|---|
| Created | 7 July 2011 |
| Updated | 6 June 2026 |
| Expires | 7 July 2027 |
| Registrar | GMO Internet Group, Inc. d/b/a Onamae.com |
| Status | client transfer prohibited |
| Nameservers | ns1.c140.mixhostcloud.jp, ns2.c140.mixhostcloud.jp |
| DNSSEC | no |
| Source | https://rdap.verisign.com/net/v1/domain/gazo-chat.net |
gazo-chat.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.
Nameserver ns1.c140.mixhostcloud.jp is published for gazo-chat.net in the registration record from https://rdap.verisign.com/net/v1/domain/gazo-chat.net.
Nameserver ns2.c140.mixhostcloud.jp is published for gazo-chat.net in the registration record from https://rdap.verisign.com/net/v1/domain/gazo-chat.net.
gazo-chat.net has 1 address record, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 172.104.64.123 |
|---|---|
| AAAA | — |
| NS | ns1.mixhostcloud.jp, ns2.mixhostcloud.jp |
| MX | gazo-chat.net (0) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at gazo-chat.net is "v=spf1 ip4:172.104.64.123 +a +mx ~all".
The DMARC text record at _dmarc.gazo-chat.net is "v=DMARC1; p=none;".
IPv4 address 172.104.64.123 answers for gazo-chat.net at resolver 1.1.1.1:53.
Mail exchanger gazo-chat.net has preference 0.
gazo-chat.net is placed in Shibuya City, Japan by the local geolocation database (db-ip).
| Address | 172.104.64.123 |
|---|---|
| Country | Japan |
| City | Shibuya City |
| Source | db-ip |
The certificate for gazo-chat.net is valid, with 36 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YR2 |
|---|---|
| Subject | gazo-chat.net |
| Valid from | 8 September 2026 |
| Valid until | 7 December 2026 |
| Days left | 36 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.gazo-chat.net, gazo-chat.net.
Tech detection checked the fetched homepage and named 6 products. Source: wappalyzergo.
Bootstrap is filed under UI frameworks.
Google Analytics is filed under Analytics.
Google Hosted Libraries is filed under CDN.
LiteSpeed is filed under Web servers.
i-mobile is filed under Advertising.
jQuery is filed under JavaScript libraries.
The homepage returned HTTP 200 in 273 ms. The target title is 37 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 273 ms |
| Title length | 37 yes |
| Quoted title | "画像チャット♪ - 見せる勇気と、見られる興奮。アダルト2ショットチャット" |
| Meta description | "画像・動画を見せ合える、匿名2ショットチャット。誰にも邪魔されない、ふたりきりの空間を今すぐ。" yes |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | ja |
| Links | 76 |
| Images | 3 |
| Favicon | no |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Family DNS for gazo-chat.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 gazo-chat.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.
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 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.
Cloudflare family DNS returned a block for gazo-chat.net. That resolver covers adult and malware names.
gazo-chat.net is placed in Shibuya City, Japan.
gazo-chat.net expires on 7 July 2027 according to https://rdap.verisign.com/net/v1/domain/gazo-chat.net.
The registry did not return a person or a company for gazo-chat.net. RDAP often redacts the registrant. The registrar on file is GMO Internet Group, Inc. d/b/a Onamae.com.
No other indexable reports share this TLD, host, or registrar yet.
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.
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.