69shu.org
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
50
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
50
69shu.org was registered on 26 Apr 2015 via GoDaddy.com, LLC and the registry expiry is 26 Apr 2027. WHOIS data came from RDAP at https://rdap.publicinterestregistry.org/rdap/domain/69shu.org.
69shu.org publishes 3 nameservers. DNSSEC is not signed.
69shu.org has 1 IPv4 address (23.248.211.166). The geolocation database places 23.248.211.166 in Los Angeles, United States.
The TLS certificate from YR1 is valid and has 86 days left (TLS 1.3).
No safety warning was recorded for 69shu.org in the checks that ran.
69shu.org was registered on 26 Apr 2015 via GoDaddy.com, LLC. The registry returned 4 status values and 3 nameservers from https://rdap.publicinterestregistry.org/rdap/domain/69shu.org.
| Registered | since 26 Apr 2015 |
|---|---|
| Created | 26 April 2015 |
| Updated | 12 August 2026 |
| Expires | 26 April 2027 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | a.dnspod.com, b.dnspod.com, c.dnspod.com |
| DNSSEC | no |
| Source | https://rdap.publicinterestregistry.org/rdap/domain/69shu.org |
69shu.org 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.
69shu.org 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.
69shu.org 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.
69shu.org 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 a.dnspod.com is published for 69shu.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/69shu.org.
Nameserver b.dnspod.com is published for 69shu.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/69shu.org.
Nameserver c.dnspod.com is published for 69shu.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/69shu.org.
69shu.org has 1 address record, 0 mail exchangers and 3 nameservers, measured at 1.1.1.1:53.
| A | 23.248.211.166 |
|---|---|
| AAAA | — |
| NS | a.dnspod.com, b.dnspod.com, c.dnspod.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 23.248.211.166 answers for 69shu.org at resolver 1.1.1.1:53.
69shu.org is placed in Los Angeles, United States by the local geolocation database (db-ip).
| Address | 23.248.211.166 |
|---|---|
| Country | United States |
| City | Los Angeles |
| Source | db-ip |
The certificate for 69shu.org is valid, with 86 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YR1 |
|---|---|
| Subject | *.69shu.org |
| Valid from | 27 October 2026 |
| Valid until | 25 January 2027 |
| Days left | 86 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.69shu.org, 69shu.org.
Tech detection checked the fetched homepage and named 0 products. Source: wappalyzergo.
The fingerprint set matched no product. That is a result, not a skipped check.
The homepage returned HTTP 403 in 1157 ms. The target title is 13 characters and the page has 1 H1 heading.
| Status | 403 |
|---|---|
| TTFB | 1157 ms |
| Title length | 13 yes |
| Quoted title | "403 Forbidden" |
| Meta description | none no |
| H1 count | 1 |
| 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.
Family DNS for 69shu.org 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.
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 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.
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
69shu.org is placed in Los Angeles, United States.
69shu.org expires on 26 April 2027 according to https://rdap.publicinterestregistry.org/rdap/domain/69shu.org.
The registry did not return a person or a company for 69shu.org. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
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.