savana.com is a live website, registered in 2004, served from Frankfurt am Main, Germany. It has a valid HTTPS certificate, 0 of 6 common security headers, 1 tracking script.
Does savana.com publish the usual trust pages?
None of about, contact, privacy or terms could be found at their usual addresses.
That is common for small or single-purpose sites, and it is also what a disposable
site looks like, so it is worth noting rather than concluding from.
These were checked at conventional paths only, so a site using different URLs may
publish them elsewhere.
How does savana.com compare with other domains analysed here?
Measured against the 74 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 49% of them (median 463ms) |
|---|---|
| Security headers | More than 0% of them |
| Domain age | Older than 61% of them |
Related domains in this index
Analysed domains sharing the same network (AS16509 Amazon.com, Inc.):
- beed.com
- eluniverso.com
- feepayer.com
- honda.com.tr
- ilbianconero.com
- ketua.com
- loans.com.au
- merrickbank.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:
- 27b.com
- beenverified.com
- bolia.com
- crunchlabs.com
- drift.com
- emojicombos.com
- fvip.com
- giftcardnest.com
Other analysed domains served from the same country:
When was savana.com registered?
savana.com was registered on 16 March 2004, which makes it about 22 years old.
A registration this old means the domain has been renewed repeatedly, which costs money every year and is not something abandoned or disposable projects tend to do.
The registrar of record is GoDaddy Online Services Cayman Islands Ltd..
Registration runs until 23 December 2031.
The domain carries 4 registry locks, which blocks unauthorised transfer or deletion.
| Registered | 16 March 2004 |
|---|---|
| Expires | 23 December 2031 |
| Registrar | GoDaddy Online Services Cayman Islands Ltd. |
| Registry status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
Where is savana.com hosted?
The first address resolves to infrastructure in Frankfurt am Main, Germany.
The network is operated by AWS CloudFront (GLOBAL) (AS16509 Amazon.com, Inc.).
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 savana.com running on?
savana.com exposes 1 identifiable technology: Cloudflare.
Cloudflare sits in front of the origin, so the server header, IP addresses and response timing describe the edge rather than the machine actually running the site.
- Cloudflare
How does the homepage respond?
The server answered with HTTP 200 over
HTTPS.
At 463ms to first byte this response is unremarkable for a homepage measured from a single European location.
The HTML weighs 107KB, which is ordinary for a homepage.
The HTML is compressed with gzip.
| Server header | cloudflare |
|---|---|
| Compression | gzip |
| Page size | 109,317 bytes |
| Declared language | not declared |
| Mobile viewport | declared |
What does the homepage say about itself?
The homepage has no title element at all, which leaves search engines to invent one from the page content.
There is no meta description, so the snippet shown in search results is assembled by the search engine from whatever text it considers relevant.
No H1 heading was found, so the page offers no single top-level statement of what it is.
The html element declares no lang attribute, which removes a signal both screen readers and translation tools rely on.
| Title | — none — (0 chars) |
|---|---|
| Meta description | — none — (0 chars) |
| H1 | — none — (0 on the page) |
| Canonical | not set |
| Open Graph title | not set |
| Headings / images | 0 H2s, 0 images (0 without alt text) |
Is savana.com served over a valid certificate?
The HTTPS certificate is issued by Amazon and is
valid until 2027-01-29, which is 116 days from the date of this check. It covers
2 hostnames.
- savana.com
- *.savana.com
The certificate has 116 days left to run.
It covers 2 hostnames, so it was issued for this site specifically.
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 savana.com?
| IP addresses | 99.84.152.99, 99.84.152.91, 99.84.152.89, 99.84.152.66 |
|---|---|
| Reverse DNS | server-99-84-152-99.fra56.r.cloudfront.net, server-99-84-152-91.fra56.r.cloudfront.net |
| Name servers | ns-1203.awsdns-22.org, ns-1671.awsdns-16.co.uk, ns-406.awsdns-50.com, ns-617.awsdns-13.net |
| Mail (MX) | smtp.google.com (pri 1) |
| SPF | v=spf1 include:_spf.google.com ~all |
| TXT records | 4 |
savana.com resolves to 4 addresses, which indicates load balancing or a CDN rather than a single origin server.
Mail is handled by 1 exchanger.
An SPF record is published, giving receiving servers a rule for which hosts may send as this domain.
Reverse DNS resolves to server-99-84-152-99.fra56.r.cloudfront.net, server-99-84-152-91.fra56.r.cloudfront.net, which usually names the hosting provider.
Who runs DNS and mail for savana.com?
DNS is operated by Amazon Route 53 rather than self-hosted name servers.
Mail is handled by Google Workspace.
No AAAA records are published, so the site is reachable over IPv4 only.
What else is worth noting about savana.com?
5 of 5 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 savana.com be spoofed in email?
DMARC is set to quarantine, so mail failing authentication is sent to spam rather than the inbox.
No CAA records are published, so any certificate authority may issue a certificate 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 1,100 bytes and names
29 user-agent groups.
It disallows all crawlers from the site root.
Sitemaps declared:
- http://www.savana.com/sitemap.xml
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 savana.com load from third parties?
The homepage pulls resources from 10 third-party hosts (analytics.twitter.com, artfut.com, base.urbanic.com, connect.facebook.net, fbefcec12443.cdn4.forter.com, googletagmanager.com). Each one sees the visitor IP and user agent on every page load.
2 cookies are set before any interaction (uuid, __cf_bm). 1 lacks the Secure flag.
The page links or refers to X/Twitter.
| Cookie | Secure | HttpOnly | SameSite |
|---|---|---|---|
| uuid | no | no | none/unset |
| __cf_bm | yes | yes | none |
Does savana.com settle on one address?
Plain HTTP redirects to HTTPS, so visitors who type the bare address still land on the secure version.
Both savana.com and www.savana.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 savana.com be crawled?
A sitemap index is served at http://www.savana.com/sitemap.xml listing 2 entries.
The most recent lastmod date in it is 2024-08-29, around 767 days ago, which suggests the site has not published anything in a while.
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 savana.com run?
1 tracking script detected: Meta Pixel.
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 savana.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?
The page pulls 2 external stylesheets and 5 external scripts, with 1 carrying defer or async.
Responses carry Cloudflare edge headers, so content is served from a CDN rather than straight from the origin.
Is savana.com accessible and current?
The page uses 0 landmark elements and 0 ARIA attributes.
The viewport tag disables pinch-zoom. That fails WCAG 1.4.4 and is a genuine problem for anyone who needs to enlarge text.
No skip-to-content link was found, which keyboard users rely on to bypass navigation.
Can search engines index savana.com?
Nothing on the homepage prevents indexing: no noindex is set in the robots meta tag or the X-Robots-Tag header.
No canonical URL is declared, which leaves duplicate addresses of this page to be resolved by the search engine.
Visible text is only 0% of the HTML, which indicates the page is assembled in the browser rather than served as content.
How is savana.com delivered?
No Cache-Control header is sent for the HTML, so caching behaviour is left to browser defaults.
HTTP/3 is advertised via alt-svc, so modern browsers will upgrade to QUIC after the first visit.
Frequently asked questions
Does savana.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 savana.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 savana.com built with?
The homepage exposes these fingerprints: Cloudflare. 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 5 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 savana.com and want this page removed.
Ask through the contact page on this site, from an address at the domain, and the report will be taken down. It only ever shows what the domain already serves publicly.
Analysed 5 October 2026.
Analyse another domain →