avgle.io
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeSSL: 33 days left8 years old
50
avgle.io was registered on 11 Dec 2017 via Tucows Domains Inc. and the registry expiry is 11 Dec 2027. WHOIS data came from RDAP at https://rdap.identitydigital.services/rdap/domain/avgle.io.
avgle.io publishes 2 nameservers. DNSSEC is not signed.
avgle.io has 2 IPv4 addresses (188.114.96.3, 188.114.97.3) and 2 IPv6 addresses (2a06:98c1:3120::4, 2a06:98c1:3121::4). The geolocation database places 188.114.96.3 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 33 days left (TLS 1.3).
No safety warning was recorded for avgle.io in the checks that ran.
Domain · RDAP/WHOIS
avgle.io was registered on 11 Dec 2017 via Tucows Domains Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.identitydigital.services/rdap/domain/avgle.io.
| Registered | since 11 Dec 2017 |
|---|---|
| Created | 11 December 2017 |
| Updated | 12 August 2026 |
| Expires | 11 December 2027 |
| Registrar | Tucows Domains Inc. |
| Status | active |
| Nameservers | walt.ns.cloudflare.com, lia.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.identitydigital.services/rdap/domain/avgle.io |
Nameserver walt.ns.cloudflare.com is published for avgle.io in the registration record from https://rdap.identitydigital.services/rdap/domain/avgle.io.
Nameserver lia.ns.cloudflare.com is published for avgle.io in the registration record from https://rdap.identitydigital.services/rdap/domain/avgle.io.
DNS
avgle.io has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 188.114.96.3, 188.114.97.3 |
|---|---|
| AAAA | 2a06:98c1:3120::4, 2a06:98c1:3121::4 |
| NS | lia.ns.cloudflare.com, walt.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.3 answers for avgle.io at resolver 1.1.1.1:53.
IPv4 address 188.114.97.3 answers for avgle.io at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3120::4 answers for avgle.io at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3121::4 answers for avgle.io at resolver 1.1.1.1:53.
Hosting and geo
avgle.io 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 avgle.io is valid, with 33 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | avgle.io |
| Valid from | 4 September 2026 |
| Valid until | 3 December 2026 |
| Days left | 33 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.avgle.io, avgle.io.
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 avgle.io 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
- October 2026: rdap created changed from 2017-12-11T06:55:09Z to 2017-12-11T06:55:09.533Z.
- October 2026: rdap dnssec changed from unknown to no.
- October 2026: rdap expires changed from 2027-12-11T06:55:09Z to 2027-12-11T06:55:09.533Z.
- October 2026: rdap statuses changed from ok to active.
- October 2026: rdap updated changed from 2026-08-12T00:06:26Z to 2026-08-12T00:06:26.206Z.
- October 2026: dns aaaa changed from 2a06:98c1:3120::3,2a06:98c1:3121::3 to 2a06:98c1:3120::4,2a06:98c1:3121::4.
- October 2026: http status_class changed from 5xx to empty.
- October 2026: tech removed Cloudflare.
- October 2026: tech removed HTTP/3.
Questions
Is avgle.io 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 avgle.io?
avgle.io is placed in Toronto, Canada.
When does avgle.io expire?
avgle.io expires on 11 December 2027 according to https://rdap.identitydigital.services/rdap/domain/avgle.io.
Who owns avgle.io?
The registry did not return a person or a company for avgle.io. RDAP often redacts the registrant. The registrar on file is Tucows Domains Inc..
Sources
- RDAP source https://rdap.identitydigital.services/rdap/domain/avgle.io at 2026-10-30T14:33:43Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:33:43Z
- TLS source tls:443 at 2026-10-30T14:33:43Z
- HTTP source https://avgle.io/ at 2026-10-30T14:33:43Z
- Tech source not available at 2026-10-30T14:33:43Z
- Geo source db-ip at 2026-10-30T14:33:43Z
- Safety source family DNS and local lists at 2026-10-30T14:33:43Z
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.