cookape.com
cookape.com is a live website, registered in 2021, served from Vilnius, Lithuania. It has a valid HTTPS certificate, 0 of 6 common security headers, 1 tracking script.
What is cookape.com about?
The words appearing most often on the homepage, excluding common filler, are a rough indication of subject matter rather than a description of the business:
- domain ×5
- website ×3
- email ×3
- hostinger ×2
- manage ×2
- business ×2
- hosting ×2
- build ×2
- secure ×2
- brand ×2
Does cookape.com publish the usual trust pages?
All four of the pages a established business normally publishes were found: about, contact, privacy and terms. These were checked at conventional paths only, so a site using different URLs may publish them elsewhere.
How does cookape.com compare with other domains analysed here?
Measured against the 121 domains in this index. This is a small, self-selected sample — the domains people happened to look up — not a representative sample of the web.
| Response time | Faster than 93% of them (median 790ms) |
|---|---|
| Security headers | More than 0% of them |
| Domain age | Older than 78% of them |
Related domains in this index
Analysed domains sharing the same network (AS47583 Hostinger International Limited):
- apkbros.com
- cbpng.com
- carmenton.xyz
- iamrestaurant.com
- mydearquotes.com
- nexyblog.com
- praiseear.co.uk
- technicalinterest.com
Sharing a network means sharing a host or CDN. It implies nothing about a relationship between the sites themselves.
Analysed domains built on a similar stack:
- jsonapi.org
- quikconsole.com
- aavot.com
- igsty.com
- structurespy.com
- techgriper.com
- techquiller.com
- techtarte.com
When was cookape.com registered?
cookape.com was registered on 17 April 2021, which makes it about 5 years old.
The registrar of record is HOSTINGER operations, UAB.
Registration runs until 17 April 2027.
The domain carries 1 registry lock, which blocks unauthorised transfer or deletion.
| Registered | 17 April 2021 |
|---|---|
| Expires | 17 April 2027 |
| Registrar | HOSTINGER operations, UAB |
| Registry status | client transfer prohibited |
Where is cookape.com hosted?
The first address resolves to infrastructure in Vilnius, Lithuania.
The network is operated by Hostinger International Limited (AS47583 Hostinger International Limited).
Hosting location describes where the responding server sits, not where the business is. A CDN will report its nearest edge rather than the origin.
What is cookape.com running on?
cookape.com exposes 1 identifiable technology: Google Analytics.
Visitor tracking is present (Google Analytics), so this homepage is not cookie-free.
- Google Analytics
How does the homepage respond?
The server answered with HTTP 200 over HTTPS.
At 85ms to first byte this response is fast for a homepage measured from a single European location.
The HTML weighs 31KB, which is ordinary for a homepage.
The HTML is compressed with gzip.
| Server header | hcdn |
|---|---|
| Compression | gzip |
| Page size | 32,079 bytes |
| Declared language | en |
| Mobile viewport | declared |
What does the homepage say about itself?
The title is 42 characters, inside the range that displays without truncation.
There is no meta description, so the snippet shown in search results is assembled by the search engine from whatever text it considers relevant.
All 1 images on the homepage have alt attributes.
| Title | Parked Domain name on Hostinger DNS system (42 chars) |
|---|---|
| Meta description | — none — (0 chars) |
| H1 | — none — (1 on the page) |
| Canonical | not set |
| Open Graph title | not set |
| Headings / images | 1 H2s, 1 images (0 without alt text) |
Is cookape.com served over a valid certificate?
The HTTPS certificate is issued by Let's Encrypt and is valid until 2026-10-22, which is 17 days from the date of this check. It covers 2 hostnames.
- cookape.com
- www.cookape.com
The certificate has 17 days left to run.
It covers 2 hostnames, so it was issued for this site specifically.
Let's Encrypt certificates are free and run on 90-day terms, so this site is almost certainly renewing automatically.
Which security headers does it set?
None of the 6 headers checked are set. That is the default state of most servers rather than evidence of a problem, but it means the browser is given no instructions it could otherwise act on.
Without HSTS, a browser that has never visited before will try HTTP first, which is the window a network attacker needs.
With no Content Security Policy, any script that reaches the page — including one injected through a compromised third-party dependency — runs with full access to it.
| Header | Set | Value |
|---|---|---|
| HSTS | no | — |
| Content Security Policy | no | — |
| X-Content-Type-Options | no | — |
| X-Frame-Options | no | — |
| Referrer-Policy | no | — |
| Permissions-Policy | no | — |
How is DNS configured for cookape.com?
| IP addresses | 2.57.91.91 |
|---|---|
| Reverse DNS | 2.57.91.91 |
| Name servers | apollo.dns-parking.com, athena.dns-parking.com |
| Mail (MX) | mx1.hostinger.com (pri 5), mx2.hostinger.com (pri 10) |
| SPF | v=spf1 include:_spf.mail.hostinger.com ~all |
| TXT records | 1 |
cookape.com resolves to a single address, so there is no DNS-level redundancy.
Mail is handled by 2 exchangers.
An SPF record is published, giving receiving servers a rule for which hosts may send as this domain.
Reverse DNS resolves to 2.57.91.91, which usually names the hosting provider.
Who runs DNS and mail for cookape.com?
Mail exchangers point at hosts that do not match any major provider, which usually means self-hosted or niche-provider mail.
No AAAA records are published, so the site is reachable over IPv4 only.
What else is worth noting about cookape.com?
1 of 1 externally hosted scripts carry no subresource integrity hash. If one of those hosts were compromised, the replacement script would run with full access to the page.
1 email address appears in the homepage markup, where address-harvesting crawlers will find it.
Can cookape.com be spoofed in email?
DMARC is published with p=none, which monitors but does not act. Forged mail is still delivered; the owner just gets reports about it.
CAA records restrict certificate issuance to 6 named authorities (issue letsencrypt.org, issuewild pki.goog, issuewild sectigo.com, issue globalsign.com), so no other CA should be able to issue for this domain.
The zone is not DNSSEC-signed. That is still the norm for most domains, but it means DNS answers cannot be cryptographically verified.
What does robots.txt allow?
robots.txt is 26 bytes and names 1 user-agent group. It disallows all crawlers from the site root.
No sitemap is declared in robots.txt.
AI crawler policy
robots.txt names no AI crawlers specifically, so they fall under whatever rule
applies to User-agent: *.
What structured data does the homepage publish?
No JSON-LD or microdata was found on the homepage.
What does cookape.com load from third parties?
The homepage pulls resources from 2 third-party hosts (fonts.googleapis.com, googletagmanager.com). Each one sees the visitor IP and user agent on every page load.
No cookies are set on first load.
Does cookape.com settle on one address?
Plain HTTP serves the site directly instead of redirecting to HTTPS. That leaves an unencrypted copy reachable and gives search engines two addresses for the same content.
Both cookape.com and www.cookape.com answer with 200 and neither redirects to the other. Search engines therefore see two complete copies of the site, and link equity is split between them unless a canonical tag resolves it.
How easily can cookape.com be crawled?
No readable sitemap was found, so crawlers have to discover every page by following links.
A deliberately invalid URL returns HTTP 200 rather than 404. That is a soft 404: every mistyped or stale link becomes an indexable page, which inflates the site with duplicates.
What tracking does cookape.com run?
1 tracking script detected: Google Analytics.
No consent management platform was detected alongside them. Where GDPR or the ePrivacy Directive applies, analytics and advertising scripts generally need consent before they load.
How does cookape.com look when shared?
No Open Graph or Twitter Card tags are present. Links shared to social platforms will fall back to whatever the platform can scrape, usually just a bare URL.
How are images, fonts and scripts handled?
1 image on the homepage, 0 of them lazy-loaded (0%).
Modern image formats are in use (1 WebP/AVIF references).
Fonts are loaded from Google Fonts, which means every page view also contacts Google. Self-hosting removes that dependency.
The page pulls 1 external stylesheet and 1 external script, with 1 carrying defer or async.
No preconnect hints are declared despite third-party scripts being present, so each new origin pays a full connection setup before it can deliver anything.
Is cookape.com accessible and current?
The page uses 0 landmark elements and 0 ARIA attributes.
There are 1 form inputs but only 0 label elements, so some fields may be unlabelled for screen readers.
No skip-to-content link was found, which keyboard users rely on to bypass navigation.
Can search engines index cookape.com?
The homepage carries a noindex directive, so it is asking search engines to keep it out of results entirely.
No canonical URL is declared, which leaves duplicate addresses of this page to be resolved by the search engine.
The homepage carries 0 internal and 5 external links across 2 outside hosts.
Visible text is only 2.8% of the HTML, which indicates the page is assembled in the browser rather than served as content.
How is cookape.com delivered?
The HTML is served with Cache-Control: no-store.
HTTP/3 is advertised via alt-svc, so modern browsers will upgrade to QUIC after the first visit.
No favicon is declared in the markup.
The TLS certificate also covers 1 subdomain: www.cookape.com.
- www.cookape.com
Frequently asked questions
Does cookape.com set the usual HTTP security headers?
It sets 0 of 6. The ones not present are: HSTS, Content Security Policy, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy.
Does cookape.com allow AI crawlers?
robots.txt names no AI crawler specifically, so they fall under the wildcard rule, which does not disallow them.
What is cookape.com built with?
The homepage exposes these fingerprints: Google Analytics. A site behind a CDN or rendered server-side may use more than it reveals.
Where does this data come from?
Every figure was measured by our own server on 4 October 2026: DNS lookups, one HTTPS request to the homepage, a TLS handshake and a request for robots.txt. No third-party SEO API is involved.
Is any of this traffic or authority data?
No. Traffic, authority and ranking figures cannot be measured by inspecting a domain, only modelled. Everything here is a direct observation.
I own cookape.com and want this page removed.
Email hello@quikconsolecom.net from an address at the domain and the report will be taken down. It only ever shows what the domain already serves publicly.
Analysed 4 October 2026. Analyse another domain →