yazhouse8.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineFamily DNS blockedSSL: 72 days left11 years oldTranco #478005
35
yazhouse8.com was registered on 5 Mar 2015 via GoDaddy.com, LLC and the registry expiry is 5 Mar 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/yazhouse8.com.
yazhouse8.com publishes 2 nameservers. DNSSEC is not signed.
yazhouse8.com has 2 IPv4 addresses (188.114.96.3, 188.114.97.3) and 2 IPv6 addresses (2a06:98c1:3120::4, 2a06:98c1:3121::4). The geolocation database places 188.114.96.3 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 72 days left (TLS 1.3).
Domain · RDAP/WHOIS
yazhouse8.com was registered on 5 Mar 2015 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/yazhouse8.com.
| Registered | since 5 Mar 2015 |
|---|---|
| Created | 5 March 2015 |
| Updated | 28 July 2026 |
| Expires | 5 March 2027 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | bayan.ns.cloudflare.com, lana.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/yazhouse8.com |
yazhouse8.com 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.
yazhouse8.com carries the status "client renew prohibited". The registrar has asked the registry to refuse a renewal. The expiry date still stands until a different status is set.
yazhouse8.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.
yazhouse8.com 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 bayan.ns.cloudflare.com is published for yazhouse8.com in the registration record from https://rdap.verisign.com/com/v1/domain/yazhouse8.com.
Nameserver lana.ns.cloudflare.com is published for yazhouse8.com in the registration record from https://rdap.verisign.com/com/v1/domain/yazhouse8.com.
DNS
yazhouse8.com has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 188.114.96.3, 188.114.97.3 |
|---|---|
| AAAA | 2a06:98c1:3120::4, 2a06:98c1:3121::4 |
| NS | bayan.ns.cloudflare.com, lana.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 188.114.96.3 answers for yazhouse8.com at resolver 1.1.1.1:53.
IPv4 address 188.114.97.3 answers for yazhouse8.com at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3120::4 answers for yazhouse8.com at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3121::4 answers for yazhouse8.com at resolver 1.1.1.1:53.
Hosting and geo
yazhouse8.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 188.114.96.3 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for yazhouse8.com is valid, with 72 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | yazhouse8.com |
| Valid from | 15 October 2026 |
| Valid until | 13 January 2027 |
| Days left | 72 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.yazhouse8.com, yazhouse8.com.
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 |
|---|
context deadline exceeded
Security
Family DNS for yazhouse8.com 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 yazhouse8.com. 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 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 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: dns aaaa changed from 2a06:98c1:3120::3,2a06:98c1:3121::3 to 2a06:98c1:3120::4,2a06:98c1:3121::4.
Questions
Is yazhouse8.com safe?
Cloudflare family DNS returned a block for yazhouse8.com. That resolver covers adult and malware names.
Who hosts yazhouse8.com?
yazhouse8.com is placed in Toronto, Canada.
When does yazhouse8.com expire?
yazhouse8.com expires on 5 March 2027 according to https://rdap.verisign.com/com/v1/domain/yazhouse8.com.
Who owns yazhouse8.com?
The registry did not return a person or a company for yazhouse8.com. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/yazhouse8.com at 2026-10-30T14:21:27Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:21:27Z
- TLS source tls:443 at 2026-10-30T14:21:27Z
- HTTP source https://yazhouse8.com/ at 2026-10-30T14:21:27Z
- Tech source not available at 2026-10-30T14:21:27Z
- Geo source db-ip at 2026-10-30T14:21:27Z
- Safety source family DNS and local lists at 2026-10-30T14:21:27Z
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.