iopq.net
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeSSL: 66 days left19 years oldTranco #139290
55
iopq.net was registered on 31 Mar 2007 via NameSilo, LLC and the registry expiry is 31 Mar 2027. WHOIS data came from RDAP at https://rdap.verisign.com/net/v1/domain/iopq.net.
iopq.net publishes 2 nameservers. DNSSEC is not signed.
iopq.net 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 66 days left (TLS 1.3).
No safety warning was recorded for iopq.net in the checks that ran.
Domain · RDAP/WHOIS
iopq.net was registered on 31 Mar 2007 via NameSilo, LLC. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/net/v1/domain/iopq.net.
| Registered | since 31 Mar 2007 |
|---|---|
| Created | 31 March 2007 |
| Updated | 17 March 2026 |
| Expires | 31 March 2027 |
| Registrar | NameSilo, LLC |
| Status | client transfer prohibited |
| Nameservers | hank.ns.cloudflare.com, sue.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/net/v1/domain/iopq.net |
iopq.net 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 hank.ns.cloudflare.com is published for iopq.net in the registration record from https://rdap.verisign.com/net/v1/domain/iopq.net.
Nameserver sue.ns.cloudflare.com is published for iopq.net in the registration record from https://rdap.verisign.com/net/v1/domain/iopq.net.
DNS
iopq.net has 4 address records, 1 mail exchanger 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 | hank.ns.cloudflare.com, sue.ns.cloudflare.com |
| MX | mx.ym.163.com (10) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at iopq.net is "v=spf1 include:spf.163.com ~all".
IPv4 address 188.114.96.4 answers for iopq.net at resolver 1.1.1.1:53.
IPv4 address 188.114.97.4 answers for iopq.net at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3120::3 answers for iopq.net at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3121::3 answers for iopq.net at resolver 1.1.1.1:53.
Mail exchanger mx.ym.163.com has preference 10.
Hosting and geo
iopq.net 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 iopq.net is valid, with 66 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | iopq.net |
| Valid from | 8 October 2026 |
| Valid until | 6 January 2027 |
| Days left | 66 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.iopq.net, iopq.net.
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 iopq.net 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 5 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::4,2a06:98c1:3121::4 to 2a06:98c1:3120::3,2a06:98c1:3121::3.
- October 2026: http status_class changed from 5xx to empty.
- October 2026: tech removed Cloudflare.
- October 2026: tech removed HTTP/3.
Questions
Is iopq.net 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 iopq.net?
iopq.net is placed in Toronto, Canada.
When does iopq.net expire?
iopq.net expires on 31 March 2027 according to https://rdap.verisign.com/net/v1/domain/iopq.net.
Who owns iopq.net?
The registry did not return a person or a company for iopq.net. RDAP often redacts the registrant. The registrar on file is NameSilo, LLC.
Sources
- RDAP source https://rdap.verisign.com/net/v1/domain/iopq.net at 2026-10-30T14:52:49Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:52:49Z
- TLS source tls:443 at 2026-10-30T14:52:49Z
- HTTP source https://iopq.net/ at 2026-10-30T14:52:49Z
- Tech source not available at 2026-10-30T14:52:49Z
- Geo source db-ip at 2026-10-30T14:52:49Z
- Safety source family DNS and local lists at 2026-10-30T14:52:49Z
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.