xxxtor.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineFamily DNS blockedSSL: 79 days left9 years oldTranco #136189
40
xxxtor.com was registered on 21 Apr 2017 via Internet Domain Service BS Corp and the registry expiry is 21 Apr 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/xxxtor.com.
xxxtor.com publishes 2 nameservers. DNSSEC is not signed.
xxxtor.com 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 79 days left (TLS 1.3).
Domain · RDAP/WHOIS
xxxtor.com was registered on 21 Apr 2017 via Internet Domain Service BS Corp. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/xxxtor.com.
| Registered | since 21 Apr 2017 |
|---|---|
| Created | 21 April 2017 |
| Updated | 22 August 2026 |
| Expires | 21 April 2027 |
| Registrar | Internet Domain Service BS Corp |
| Status | client transfer prohibited |
| Nameservers | bowen.ns.cloudflare.com, pat.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/xxxtor.com |
xxxtor.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 bowen.ns.cloudflare.com is published for xxxtor.com in the registration record from https://rdap.verisign.com/com/v1/domain/xxxtor.com.
Nameserver pat.ns.cloudflare.com is published for xxxtor.com in the registration record from https://rdap.verisign.com/com/v1/domain/xxxtor.com.
DNS
xxxtor.com 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 | bowen.ns.cloudflare.com, pat.ns.cloudflare.com |
| MX | _dc-mx.a49e3e56054d.xxxtor.com (10) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at xxxtor.com is "v=spf1 +mx +a:xxxtor.com -all".
IPv4 address 188.114.96.4 answers for xxxtor.com at resolver 1.1.1.1:53.
IPv4 address 188.114.97.4 answers for xxxtor.com at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3120::3 answers for xxxtor.com at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3121::3 answers for xxxtor.com at resolver 1.1.1.1:53.
Mail exchanger _dc-mx.a49e3e56054d.xxxtor.com has preference 10.
Hosting and geo
xxxtor.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 xxxtor.com is valid, with 79 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | xxxtor.com |
| Valid from | 20 October 2026 |
| Valid until | 18 January 2027 |
| Days left | 79 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.xxxtor.com, xxxtor.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 |
|---|
Get "https://xxxtor.com/": context deadline exceeded
Security
Family DNS for xxxtor.com is blocked, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | blocked |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Cloudflare family DNS returned a block for xxxtor.com. That resolver covers adult and malware names.
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 0 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: http status_class changed from 2xx to empty.
- October 2026: tech removed Cloudflare.
- October 2026: tech removed HTTP/3.
- October 2026: tech removed Liveinternet.
- October 2026: tech removed jQuery.
Questions
Is xxxtor.com safe?
Cloudflare family DNS returned a block for xxxtor.com. That resolver covers adult and malware names.
Who hosts xxxtor.com?
xxxtor.com is placed in Toronto, Canada.
When does xxxtor.com expire?
xxxtor.com expires on 21 April 2027 according to https://rdap.verisign.com/com/v1/domain/xxxtor.com.
Who owns xxxtor.com?
The registry did not return a person or a company for xxxtor.com. RDAP often redacts the registrant. The registrar on file is Internet Domain Service BS Corp.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/xxxtor.com at 2026-10-30T14:21:16Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:21:16Z
- TLS source tls:443 at 2026-10-30T14:21:16Z
- HTTP source https://xxxtor.com/ at 2026-10-30T14:21:16Z
- Tech source not available at 2026-10-30T14:21:16Z
- Geo source db-ip at 2026-10-30T14:21:16Z
- Safety source family DNS and local lists at 2026-10-30T14:21:16Z
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.