oaifree.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeSSL: 88 days left2 years old
60
oaifree.com was registered on 5 Dec 2023 via Cloudflare, Inc. and the registry expiry is 5 Dec 2026. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/oaifree.com.
oaifree.com publishes 2 nameservers. DNSSEC is signed.
oaifree.com has 2 IPv4 addresses (188.114.96.4, 188.114.97.4) and 2 IPv6 addresses (2a06:98c1:3120::4, 2a06:98c1:3121::4). The geolocation database places 188.114.96.4 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 88 days left (TLS 1.3).
No safety warning was recorded for oaifree.com in the checks that ran.
Domain · RDAP/WHOIS
oaifree.com was registered on 5 Dec 2023 via Cloudflare, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/oaifree.com.
| Registered | since 5 Dec 2023 |
|---|---|
| Created | 5 December 2023 |
| Updated | 5 November 2025 |
| Expires | 5 December 2026 |
| Registrar | Cloudflare, Inc. |
| Status | client transfer prohibited |
| Nameservers | dahlia.ns.cloudflare.com, marek.ns.cloudflare.com |
| DNSSEC | yes |
| Source | https://rdap.verisign.com/com/v1/domain/oaifree.com |
oaifree.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.
Nameserver dahlia.ns.cloudflare.com is published for oaifree.com in the registration record from https://rdap.verisign.com/com/v1/domain/oaifree.com.
Nameserver marek.ns.cloudflare.com is published for oaifree.com in the registration record from https://rdap.verisign.com/com/v1/domain/oaifree.com.
DNS
oaifree.com has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 188.114.96.4, 188.114.97.4 |
|---|---|
| AAAA | 2a06:98c1:3120::4, 2a06:98c1:3121::4 |
| NS | dahlia.ns.cloudflare.com, marek.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | issue comodoca.com, issue digicert.com; cansignhttpexchanges=yes, issue letsencrypt.org, issue pki.goog; cansignhttpexchanges=yes, issue ssl.com, issuewild comodoca.com, issuewild digicert.com; cansignhttpexchanges=yes, issuewild letsencrypt.org, issuewild pki.goog; cansignhttpexchanges=yes, issuewild ssl.com |
| Wildcard | off |
| DNSSEC | signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 188.114.96.4 answers for oaifree.com at resolver 1.1.1.1:53.
IPv4 address 188.114.97.4 answers for oaifree.com at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3120::4 answers for oaifree.com at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3121::4 answers for oaifree.com at resolver 1.1.1.1:53.
Hosting and geo
oaifree.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 188.114.96.4 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for oaifree.com is valid, with 88 days left and 1 subject alternative name. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | oaifree.com |
| Valid from | 29 October 2026 |
| Valid until | 27 January 2027 |
| Days left | 88 |
| SAN count | 1 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: oaifree.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 oaifree.com 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 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 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.
Change history
- October 2026: dns a changed from 188.114.96.3,188.114.97.3 to 188.114.96.4,188.114.97.4.
- 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 oaifree.com 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 oaifree.com?
oaifree.com is placed in Toronto, Canada.
When does oaifree.com expire?
oaifree.com expires on 5 December 2026 according to https://rdap.verisign.com/com/v1/domain/oaifree.com.
Who owns oaifree.com?
The registry did not return a person or a company for oaifree.com. RDAP often redacts the registrant. The registrar on file is Cloudflare, Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/oaifree.com at 2026-10-30T14:07:45Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:07:45Z
- TLS source tls:443 at 2026-10-30T14:07:45Z
- HTTP source https://oaifree.com/ at 2026-10-30T14:07:45Z
- Tech source not available at 2026-10-30T14:07:45Z
- Geo source db-ip at 2026-10-30T14:07:45Z
- Safety source family DNS and local lists at 2026-10-30T14:07:45Z
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.