aquipelis.org
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeSSL: 60 days leftUnder 1 year old
47
aquipelis.org was registered on 1 Jun 2026 via Gname 310 Inc and the registry expiry is 1 Jun 2027. WHOIS data came from RDAP at https://rdap.publicinterestregistry.org/rdap/domain/aquipelis.org.
aquipelis.org publishes 2 nameservers. DNSSEC is not signed.
aquipelis.org has 2 IPv4 addresses (188.114.96.4, 188.114.97.4) and 2 IPv6 addresses (2a06:98c1:3120::3, 2a06:98c1:3121::3). The geolocation database places 188.114.96.4 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 60 days left (TLS 1.3).
No safety warning was recorded for aquipelis.org in the checks that ran.
Domain · RDAP/WHOIS
aquipelis.org was registered on 1 Jun 2026 via Gname 310 Inc. The registry returned 1 status value and 2 nameservers from https://rdap.publicinterestregistry.org/rdap/domain/aquipelis.org.
| Registered | since 1 Jun 2026 |
|---|---|
| Created | 1 June 2026 |
| Updated | 12 August 2026 |
| Expires | 1 June 2027 |
| Registrar | Gname 310 Inc |
| Status | client transfer prohibited |
| Nameservers | aron.ns.cloudflare.com, theo.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.publicinterestregistry.org/rdap/domain/aquipelis.org |
aquipelis.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 aron.ns.cloudflare.com is published for aquipelis.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/aquipelis.org.
Nameserver theo.ns.cloudflare.com is published for aquipelis.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/aquipelis.org.
DNS
aquipelis.org 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::3, 2a06:98c1:3121::3 |
| NS | aron.ns.cloudflare.com, theo.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.4 answers for aquipelis.org at resolver 1.1.1.1:53.
IPv4 address 188.114.97.4 answers for aquipelis.org at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3120::3 answers for aquipelis.org at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3121::3 answers for aquipelis.org at resolver 1.1.1.1:53.
Hosting and geo
aquipelis.org 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 aquipelis.org is valid, with 60 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | aquipelis.org |
| Valid from | 1 October 2026 |
| Valid until | 30 December 2026 |
| Days left | 60 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.aquipelis.org, aquipelis.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://aquipelis.org/": context deadline exceeded
Security
Family DNS for aquipelis.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 2 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::4,2a06:98c1:3121::4 to 2a06:98c1:3120::3,2a06:98c1:3121::3.
- October 2026: http status_class changed from 2xx to empty.
- October 2026: tech removed Cloudflare.
- October 2026: tech removed HTTP/3.
Questions
Is aquipelis.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 aquipelis.org?
aquipelis.org is placed in Toronto, Canada.
When does aquipelis.org expire?
aquipelis.org expires on 1 June 2027 according to https://rdap.publicinterestregistry.org/rdap/domain/aquipelis.org.
Who owns aquipelis.org?
The registry did not return a person or a company for aquipelis.org. RDAP often redacts the registrant. The registrar on file is Gname 310 Inc.
Sources
- RDAP source https://rdap.publicinterestregistry.org/rdap/domain/aquipelis.org at 2026-10-30T15:01:15Z
- DNS source 1.1.1.1:53 at 2026-10-30T15:01:15Z
- TLS source tls:443 at 2026-10-30T15:01:15Z
- HTTP source https://aquipelis.org/ at 2026-10-30T15:01:15Z
- Tech source not available at 2026-10-30T15:01:15Z
- Geo source db-ip at 2026-10-30T15:01:15Z
- Safety source family DNS and local lists at 2026-10-30T15:01:15Z
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.