xtapes.to
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
HTTP 403Family DNS blockedSSL: 42 days left1 year old
40
xtapes.to was registered on 19 Jun 2025 via EuroDNS S.A. and the registry expiry is 19 Jun 2027. WHOIS data came from RDAP at https://rdap.tonicregistry.to/rdap/domain/xtapes.to.
xtapes.to publishes 4 nameservers. DNSSEC is not signed.
xtapes.to has 1 IPv4 address (18.223.197.26). The geolocation database places 18.223.197.26 in Dublin, United States.
The TLS certificate from YR1 is valid and has 42 days left (TLS 1.3).
Tech detection named HSTS. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
xtapes.to was registered on 19 Jun 2025 via EuroDNS S.A.. The registry returned 1 status value and 4 nameservers from https://rdap.tonicregistry.to/rdap/domain/xtapes.to.
| Registered | since 19 Jun 2025 |
|---|---|
| Created | 19 June 2025 |
| Updated | 9 January 2026 |
| Expires | 19 June 2027 |
| Registrar | EuroDNS S.A. |
| Status | active |
| Nameservers | ns-531.awsdns-02.net, ns-92.awsdns-11.com, sdns3.ultradns.biz, sdns3.ultradns.com |
| DNSSEC | no |
| Source | https://rdap.tonicregistry.to/rdap/domain/xtapes.to |
Nameserver ns-531.awsdns-02.net is published for xtapes.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/xtapes.to.
Nameserver ns-92.awsdns-11.com is published for xtapes.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/xtapes.to.
Nameserver sdns3.ultradns.biz is published for xtapes.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/xtapes.to.
Nameserver sdns3.ultradns.com is published for xtapes.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/xtapes.to.
DNS
xtapes.to has 1 address record, 0 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 18.223.197.26 |
|---|---|
| AAAA | — |
| NS | ns-531.awsdns-02.net, ns-92.awsdns-11.com, sdns3.ultradns.biz, sdns3.ultradns.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 18.223.197.26 answers for xtapes.to at resolver 1.1.1.1:53.
Hosting and geo
xtapes.to is placed in Dublin, United States by the local geolocation database (db-ip).
| Address | 18.223.197.26 |
|---|---|
| Country | United States |
| City | Dublin |
| Source | db-ip |
SSL/TLS
The certificate for xtapes.to is valid, with 42 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YR1 |
|---|---|
| Subject | xtapes.to |
| Valid from | 14 September 2026 |
| Valid until | 13 December 2026 |
| Days left | 42 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: www.xtapes.to, xtapes.to.
Tech stack
Tech detection checked the fetched homepage and named 1 product. Source: wappalyzergo.
- HSTS · Security
HSTS is filed under Security.
On-page checks
The homepage returned HTTP 403 in 108 ms. The target title is 24 characters and the page has 3 H1 headings.
| Status | 403 |
|---|---|
| TTFB | 108 ms |
| Title length | 24 yes |
| Quoted title | "Down for Maintenance 403" |
| Meta description | none no |
| H1 count | 3 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 4 |
| Images | 0 |
| Favicon | no |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Security
Family DNS for xtapes.to 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 | yes |
| CSP | no |
Cloudflare family DNS returned a block for xtapes.to. 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 0 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 5 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: geo city changed from empty to Dublin.
- October 2026: geo country changed from empty to United States.
Questions
Is xtapes.to safe?
Cloudflare family DNS returned a block for xtapes.to. That resolver covers adult and malware names.
Who hosts xtapes.to?
xtapes.to is placed in Dublin, United States.
When does xtapes.to expire?
xtapes.to expires on 19 June 2027 according to https://rdap.tonicregistry.to/rdap/domain/xtapes.to.
Who owns xtapes.to?
The registry did not return a person or a company for xtapes.to. RDAP often redacts the registrant. The registrar on file is EuroDNS S.A..
Sources
- RDAP source https://rdap.tonicregistry.to/rdap/domain/xtapes.to at 2026-10-30T15:18:59Z
- DNS source 1.1.1.1:53 at 2026-10-30T15:18:59Z
- TLS source tls:443 at 2026-10-30T15:18:59Z
- HTTP source https://xtapes.to/ at 2026-10-30T15:18:59Z
- Tech source wappalyzergo at 2026-10-30T15:18:59Z
- Geo source db-ip at 2026-10-30T15:18:59Z
- Safety source family DNS and local lists at 2026-10-30T15:18:59Z
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.