gooool.org
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeSSL: 68 days left14 years old
50
gooool.org was registered on 12 Jun 2012 via Eranet International Limited and the registry expiry is 12 Jun 2027. WHOIS data came from RDAP at https://rdap.publicinterestregistry.org/rdap/domain/gooool.org.
gooool.org publishes 2 nameservers. DNSSEC is not signed.
gooool.org has 2 IPv4 addresses (188.114.96.3, 188.114.97.3). The geolocation database places 188.114.96.3 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 68 days left (TLS 1.3).
No safety warning was recorded for gooool.org in the checks that ran.
Domain · RDAP/WHOIS
gooool.org was registered on 12 Jun 2012 via Eranet International Limited. The registry returned 1 status value and 2 nameservers from https://rdap.publicinterestregistry.org/rdap/domain/gooool.org.
| Registered | since 12 Jun 2012 |
|---|---|
| Created | 12 June 2012 |
| Updated | 12 August 2026 |
| Expires | 12 June 2027 |
| Registrar | Eranet International Limited |
| Status | client transfer prohibited |
| Nameservers | max.ns.cloudflare.com, olga.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.publicinterestregistry.org/rdap/domain/gooool.org |
gooool.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.
Nameserver max.ns.cloudflare.com is published for gooool.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/gooool.org.
Nameserver olga.ns.cloudflare.com is published for gooool.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/gooool.org.
DNS
gooool.org has 2 address records, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 188.114.96.3, 188.114.97.3 |
|---|---|
| AAAA | — |
| NS | max.ns.cloudflare.com, olga.ns.cloudflare.com |
| MX | mx.yandex.ru (10) |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 188.114.96.3 answers for gooool.org at resolver 1.1.1.1:53.
IPv4 address 188.114.97.3 answers for gooool.org at resolver 1.1.1.1:53.
Mail exchanger mx.yandex.ru has preference 10.
Hosting and geo
gooool.org 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 gooool.org is valid, with 68 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | gooool.org |
| Valid from | 9 October 2026 |
| Valid until | 7 January 2027 |
| Days left | 68 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.gooool.org, gooool.org.
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://gooool365.com/": stream error: stream ID 3; PROTOCOL_ERROR; received from peer
Security
Family DNS for gooool.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.
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 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
First checked on 30 October 2026; changes will appear here.
Questions
Is gooool.org 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 gooool.org?
gooool.org is placed in Toronto, Canada.
When does gooool.org expire?
gooool.org expires on 12 June 2027 according to https://rdap.publicinterestregistry.org/rdap/domain/gooool.org.
Who owns gooool.org?
The registry did not return a person or a company for gooool.org. RDAP often redacts the registrant. The registrar on file is Eranet International Limited.
Sources
- RDAP source https://rdap.publicinterestregistry.org/rdap/domain/gooool.org at 2026-10-30T15:02:19Z
- DNS source 1.1.1.1:53 at 2026-10-30T15:02:19Z
- TLS source tls:443 at 2026-10-30T15:02:19Z
- HTTP source https://gooool.org/ at 2026-10-30T15:02:19Z
- Tech source not available at 2026-10-30T15:02:19Z
- Geo source db-ip at 2026-10-30T15:02:19Z
- Safety source family DNS and local lists at 2026-10-30T15:02:19Z
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.