okztwo.me
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeUnder 1 year old
27
okztwo.me was registered on 22 Dec 2025 via Dynadot Inc and the registry expiry is 22 Dec 2026. WHOIS data came from RDAP at https://rdap.identitydigital.services/rdap/domain/okztwo.me.
okztwo.me publishes 2 nameservers. DNSSEC is not signed.
okztwo.me has 1 IPv4 address (178.98.18.165). The geolocation database places 178.98.18.165 in Los Angeles (Westlake), United States.
No safety warning was recorded for okztwo.me in the checks that ran.
Domain · RDAP/WHOIS
okztwo.me was registered on 22 Dec 2025 via Dynadot Inc. The registry returned 1 status value and 2 nameservers from https://rdap.identitydigital.services/rdap/domain/okztwo.me.
| Registered | since 22 Dec 2025 |
|---|---|
| Created | 22 December 2025 |
| Updated | 11 August 2026 |
| Expires | 22 December 2026 |
| Registrar | Dynadot Inc |
| Status | client transfer prohibited |
| Nameservers | ns1.alidns.com, ns2.alidns.com |
| DNSSEC | no |
| Source | https://rdap.identitydigital.services/rdap/domain/okztwo.me |
okztwo.me 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.alidns.com is published for okztwo.me in the registration record from https://rdap.identitydigital.services/rdap/domain/okztwo.me.
Nameserver ns2.alidns.com is published for okztwo.me in the registration record from https://rdap.identitydigital.services/rdap/domain/okztwo.me.
DNS
okztwo.me has 1 address record, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 178.98.18.165 |
|---|---|
| AAAA | — |
| NS | ns1.alidns.com, ns2.alidns.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 178.98.18.165 answers for okztwo.me at resolver 1.1.1.1:53.
Hosting and geo
okztwo.me is placed in Los Angeles (Westlake), United States by the local geolocation database (db-ip).
| Address | 178.98.18.165 |
|---|---|
| Country | United States |
| City | Los Angeles (Westlake) |
| Source | db-ip |
SSL/TLS
No TLS certificate was read for okztwo.me on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
dial tcp 178.98.18.165:443: connect: connection refused
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://okztwo.me/": dial tcp 178.98.18.165:443: connect: connection refused
Security
Family DNS for okztwo.me 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 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 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 2 of 5. Five points at one year, two points at 30 days.
Change history
- October 2026: rdap created changed from 2025-12-22T01:10:21Z to 2025-12-22T01:10:21.864Z.
- October 2026: rdap dnssec changed from unknown to no.
- October 2026: rdap expires changed from 2026-12-22T01:10:21Z to 2026-12-22T01:10:21.864Z.
- October 2026: rdap statuses changed from clienttransferprohibited to client transfer prohibited.
- October 2026: rdap updated changed from 2026-08-11T00:23:34Z to 2026-08-11T00:23:34.688Z.
- October 2026: geo city changed from empty to Los Angeles (Westlake).
- October 2026: geo country changed from empty to United States.
Questions
Is okztwo.me 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 okztwo.me?
okztwo.me is placed in Los Angeles (Westlake), United States.
When does okztwo.me expire?
okztwo.me expires on 22 December 2026 according to https://rdap.identitydigital.services/rdap/domain/okztwo.me.
Who owns okztwo.me?
The registry did not return a person or a company for okztwo.me. RDAP often redacts the registrant. The registrar on file is Dynadot Inc.
Sources
- RDAP source https://rdap.identitydigital.services/rdap/domain/okztwo.me at 2026-10-30T14:44:22Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:44:22Z
- TLS source tls:443 at 2026-10-30T14:44:22Z
- HTTP source https://okztwo.me/ at 2026-10-30T14:44:22Z
- Tech source not available at 2026-10-30T14:44:22Z
- Geo source db-ip at 2026-10-30T14:44:22Z
- Safety source family DNS and local lists at 2026-10-30T14:44:22Z
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.