cuevana.pizza
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 42 days leftUnder 1 year old
67
cuevana.pizza was registered on 5 May 2026 via GoDaddy.com, LLC and the registry expiry is 5 May 2027. WHOIS data came from RDAP at https://rdap.identitydigital.services/rdap/domain/cuevana.pizza.
cuevana.pizza publishes 2 nameservers. DNSSEC is not signed.
cuevana.pizza has 2 IPv4 addresses (104.21.75.244, 172.67.184.11) and 2 IPv6 addresses (2606:4700:3031::ac43:b80b, 2606:4700:3037::6815:4bf4). The geolocation database places 104.21.75.244 in Toronto, Canada.
The TLS certificate from YE1 is valid and has 42 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named AMP, Cart Functionality, Cloudflare, Cloudflare Browser Insights, Google Analytics, Google Analytics Enhanced eCommerce, HSTS, HTTP/3, Ruby and Ruby on Rails. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for cuevana.pizza in the checks that ran.
Domain · RDAP/WHOIS
cuevana.pizza was registered on 5 May 2026 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.identitydigital.services/rdap/domain/cuevana.pizza.
| Registered | since 5 May 2026 |
|---|---|
| Created | 5 May 2026 |
| Updated | 13 August 2026 |
| Expires | 5 May 2027 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | norman.ns.cloudflare.com, harleigh.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.identitydigital.services/rdap/domain/cuevana.pizza |
cuevana.pizza carries the status "client delete prohibited". The registrar has asked the registry to refuse a delete. This is an EPP status on the domain object. It does not say the website is safe, and it does not name the person who registered it.
cuevana.pizza carries the status "client renew prohibited". The registrar has asked the registry to refuse a renewal. The expiry date still stands until a different status is set.
cuevana.pizza 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.
cuevana.pizza carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.
Nameserver norman.ns.cloudflare.com is published for cuevana.pizza in the registration record from https://rdap.identitydigital.services/rdap/domain/cuevana.pizza.
Nameserver harleigh.ns.cloudflare.com is published for cuevana.pizza in the registration record from https://rdap.identitydigital.services/rdap/domain/cuevana.pizza.
DNS
cuevana.pizza has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.75.244, 172.67.184.11 |
|---|---|
| AAAA | 2606:4700:3031::ac43:b80b, 2606:4700:3037::6815:4bf4 |
| NS | harleigh.ns.cloudflare.com, norman.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.21.75.244 answers for cuevana.pizza at resolver 1.1.1.1:53.
IPv4 address 172.67.184.11 answers for cuevana.pizza at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3031::ac43:b80b answers for cuevana.pizza at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3037::6815:4bf4 answers for cuevana.pizza at resolver 1.1.1.1:53.
Hosting and geo
cuevana.pizza is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.75.244 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for cuevana.pizza is valid, with 42 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YE1 |
|---|---|
| Subject | cuevana.pizza |
| 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: *.cuevana.pizza, cuevana.pizza.
Tech stack
Tech detection checked the fetched homepage and named 10 products. Source: wappalyzergo.
- AMP · JavaScript frameworks
- Cart Functionality · Ecommerce
- Cloudflare · CDN
- Cloudflare Browser Insights · Analytics, RUM
- Google Analytics · Analytics
- Google Analytics Enhanced eCommerce · Analytics
- HSTS · Security
- HTTP/3 · Miscellaneous
- Ruby · Programming languages
- Ruby on Rails · Web frameworks
AMP is filed under JavaScript frameworks.
Cart Functionality is filed under Ecommerce.
Cloudflare is filed under CDN.
Cloudflare Browser Insights is filed under Analytics, RUM.
Google Analytics is filed under Analytics.
Google Analytics Enhanced eCommerce is filed under Analytics.
HSTS is filed under Security.
HTTP/3 is filed under Miscellaneous.
Ruby is filed under Programming languages.
Ruby on Rails is filed under Web frameworks.
On-page checks
The homepage returned HTTP 200 in 25 ms. The target title is 59 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 25 ms |
| Title length | 59 yes |
| Quoted title | "SKY77: Daring Transaksi Depo Singkat Sistem GPI Version 2.0" |
| Meta description | none no |
| H1 count | 0 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | index,follow |
| Canonical | https://sky77gacor.asia/game/gpi/2 |
| Language | en |
| Links | 192 |
| Images | 20 |
| Favicon | yes |
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 cuevana.pizza 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 | yes |
| 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 25 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 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
First checked on 30 October 2026; changes will appear here.
Questions
Is cuevana.pizza 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 cuevana.pizza?
cuevana.pizza is placed in Toronto, Canada.
When does cuevana.pizza expire?
cuevana.pizza expires on 5 May 2027 according to https://rdap.identitydigital.services/rdap/domain/cuevana.pizza.
Who owns cuevana.pizza?
The registry did not return a person or a company for cuevana.pizza. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.identitydigital.services/rdap/domain/cuevana.pizza at 2026-10-30T15:56:03Z
- DNS source 1.1.1.1:53 at 2026-10-30T15:56:03Z
- TLS source tls:443 at 2026-10-30T15:56:03Z
- HTTP source https://cuevana.pizza/ at 2026-10-30T15:56:03Z
- Tech source wappalyzergo at 2026-10-30T15:56:03Z
- Geo source db-ip at 2026-10-30T15:56:03Z
- Safety source family DNS and local lists at 2026-10-30T15:56:03Z
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.