saveas.com is a live website, registered in 1999, served from Jacksonville, United States. It has a valid HTTPS certificate, 0 of 6 common security headers.
Does saveas.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 saveas.com compare with other domains analysed here?
Measured against the 81 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 5% of them (median 491ms) |
|---|---|
| Security headers | More than 0% of them |
| Domain age | Older than 67% of them |
Related domains in this index
Other analysed domains served from the same country:
When was saveas.com registered?
saveas.com was registered on 2 January 1999, which makes it about 27 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 Network Solutions, LLC.
Registration runs until 2 January 2031.
The domain carries 1 registry lock, which blocks unauthorised transfer or deletion.
| Registered | 2 January 1999 |
|---|---|
| Expires | 2 January 2031 |
| Registrar | Network Solutions, LLC |
| Registry status | client transfer prohibited |
Where is saveas.com hosted?
The first address resolves to infrastructure in Jacksonville, United States.
The network is operated by Network Solutions, LLC (AS40034 Confluence Networks 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 saveas.com running on?
No platform, framework or analytics fingerprints were found in the homepage markup of saveas.com. That usually means hand-written HTML, an uncommon stack, or a page assembled entirely at the edge.
No recognisable platform, framework or analytics fingerprints were found in the homepage markup.
How does the homepage respond?
The server answered with HTTP 200 over
HTTP.
At 5862ms to first byte this response is very slow for a homepage measured from a single European location.
The HTML weighs 27KB, which is ordinary for a homepage.
The HTML is compressed with gzip.
| Server header | nginx/1.28.0 |
|---|---|
| Compression | gzip |
| Page size | 27,276 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.
1 of 1 images carry no alt attribute, which leaves them unreadable to screen readers and uninterpretable to image search.
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, 1 images (1 without alt text) |
Is saveas.com served over a valid certificate?
The HTTPS certificate is issued by ZeroSSL GmbH and is
valid until 2026-11-08, which is 34 days from the date of this check. It covers
1 hostname.
- saveas.com
The certificate has 34 days left to run.
It covers 1 hostname, 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 saveas.com?
| IP addresses | 208.91.197.27 |
|---|---|
| Reverse DNS | 208.91.197.27 |
| Name servers | ns58.worldnic.com, ns57.worldnic.com |
| Mail (MX) | no mail records |
| SPF | not published |
| TXT records | 0 |
saveas.com resolves to a single address, so there is no DNS-level redundancy.
No MX records are published, so this domain does not receive mail at its apex. Mail sent to it will bounce.
No SPF record is published. Receiving servers therefore have no published rule for who may send mail as this domain, which makes spoofing it materially easier.
Reverse DNS resolves to 208.91.197.27, which usually names the hosting provider.
Who runs DNS and mail for saveas.com?
No AAAA records are published, so the site is reachable over IPv4 only.
Can saveas.com be spoofed in email?
No DMARC record is published, so there is no instruction telling receiving servers what to do with mail that fails authentication. In practice that means forged mail from this domain is likely to be delivered.
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?
No robots.txt was served. Crawlers treat a missing file as permission to crawl
everything, so this is an open crawl policy by default rather than a blocked one.
What structured data does the homepage publish?
No JSON-LD or microdata was found on the homepage.
What does saveas.com load from third parties?
The homepage pulls resources from 1 third-party host (l.cdn-fileserver.com). Each one sees the visitor IP and user agent on every page load.
No cookies are set on first load.
Does saveas.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 saveas.com and www.saveas.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 saveas.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 saveas.com run?
No analytics or advertising trackers were detected on the homepage of saveas.com, which is unusual for a commercial site.
How does saveas.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%).
No srcset attributes are used, so every device is served the same image size regardless of screen.
The page pulls 0 external stylesheets and 0 external scripts, with 0 carrying defer or async.
Is saveas.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 saveas.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.2% of the HTML, which indicates the page is assembled in the browser rather than served as content.
How is saveas.com delivered?
No Cache-Control header is sent for the HTML, so caching behaviour is left to browser defaults.
No favicon is declared in the markup.
Frequently asked questions
Does saveas.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 saveas.com allow AI crawlers?
No robots.txt is served, so nothing is disallowed and AI crawlers are free to read the site.
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 saveas.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 →