reve.com describes itself as "Reve: Reimagine reality. Create, edit, and remix images. Combine natural-language edits with a drag-and-drop image editor.". It was registered in 1999, served from Kansas City, United States. It has a valid HTTPS certificate, 2 of 6 common security headers, 1 tracking script.
What is reve.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:
- reve ×2
- model ×2
Does reve.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 reve.com compare with other domains analysed here?
Measured against the 76 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 26% of them (median 443ms) |
|---|---|
| Security headers | More than 60% of them |
| Domain age | Older than 66% of them |
Related domains in this index
Analysed domains built on a similar stack:
Other analysed domains served from the same country:
When was reve.com registered?
reve.com was registered on 3 December 1999, which makes it about 26 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 Gandi SAS.
Registration expires in 13 days (3 December 2026), which is close enough that a missed renewal would take the site offline.
The domain carries 4 registry locks, which blocks unauthorised transfer or deletion.
| Registered | 3 December 1999 |
|---|---|
| Expires | 3 December 2026 |
| Registrar | Gandi SAS |
| Registry status | client transfer prohibited, server delete prohibited, server transfer prohibited, server update prohibited |
Where is reve.com hosted?
The first address resolves to infrastructure in Kansas City, United States.
The network is operated by Google Cloud (AS396982 Google LLC).
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 reve.com running on?
reve.com exposes 1 identifiable technology: Google Tag Manager.
Visitor tracking is present (Google Tag Manager), so this homepage is not cookie-free.
- Google Tag Manager
How does the homepage respond?
The server answered with HTTP 200 over
HTTPS.
At 830ms to first byte this response is slow for a homepage measured from a single European location.
The HTML weighs 38KB, which is ordinary for a homepage.
No compression is applied to the HTML. Enabling gzip or brotli usually cuts transfer size by around two thirds at no cost to the server.
| Server header | nginx |
|---|---|
| Compression | none |
| Page size | 39,187 bytes |
| Declared language | en-US |
| Mobile viewport | declared |
What does the homepage say about itself?
The title is only 18 characters, which is short enough that it probably is not describing the page so much as naming it.
A meta description of 122 characters is present.
All 13 images on the homepage have alt attributes.
| Title | Reve Image – Model (18 chars) |
|---|---|
| Meta description | Reve: Reimagine reality. Create, edit, and remix images. Combine natural-language edits with a drag-and-drop image editor. (122 chars) |
| H1 | See your Ideas (1 on the page) |
| Canonical | not set |
| Open Graph title | Reve: Reimagine Reality |
| Headings / images | 0 H2s, 13 images (0 without alt text) |
Is reve.com served over a valid certificate?
The HTTPS certificate is issued by Google Trust Services and is
valid until 2026-11-16, which is 42 days from the date of this check. It covers
2 hostnames.
- reve.com
- *.reve.com
The certificate has 42 days left to run.
It covers 2 hostnames, so it was issued for this site specifically.
Which security headers does it set?
2 of 6 are set (Content Security Policy, X-Frame-Options). Absent: HSTS, X-Content-Type-Options, Referrer-Policy, Permissions-Policy.
Without HSTS, a browser that has never visited before will try HTTP first, which is the window a network attacker needs.
| Header | Set | Value |
|---|---|---|
| HSTS | no | — |
| Content Security Policy | yes | default-src 'none'; base-uri 'none'; object-src 'none'; frame-ancestors 'self'; form-action 'self' https://www.facebook. |
| X-Content-Type-Options | no | — |
| X-Frame-Options | yes | SAMEORIGIN |
| Referrer-Policy | no | — |
| Permissions-Policy | no | — |
How is DNS configured for reve.com?
| IP addresses | 34.111.54.145 |
|---|---|
| Reverse DNS | 145.54.111.34.bc.googleusercontent.com |
| Name servers | ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com |
| Mail (MX) | alt4.aspmx.l.google.com (pri 10), alt2.aspmx.l.google.com (pri 5), aspmx.l.google.com (pri 1), alt3.aspmx.l.google.com (pri 10), alt1.aspmx.l.google.com (pri 5) |
| SPF | v=spf1 include:_spf.google.com include:mail.zendesk.com ~all |
| TXT records | 3 |
reve.com resolves to a single address, so there is no DNS-level redundancy.
Mail is handled by 5 exchangers.
An SPF record is published, giving receiving servers a rule for which hosts may send as this domain.
Reverse DNS resolves to 145.54.111.34.bc.googleusercontent.com, which usually names the hosting provider.
Who runs DNS and mail for reve.com?
DNS is operated by Google Cloud DNS 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.
Can reve.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?
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?
- WebApplication
- Offer
- Organization
The homepage publishes 3 structured data types: WebApplication, Offer, Organization.
What does reve.com load from third parties?
The homepage pulls resources from 2 third-party hosts (101555001786.collect.observeinc.com, googletagmanager.com). Each one sees the visitor IP and user agent on every page load.
No cookies are set on first load.
Does reve.com settle on one address?
Plain HTTP redirects to HTTPS, so visitors who type the bare address still land on the secure version.
The www address redirects to https://app.reve.com/, so the site settles on one canonical hostname.
How easily can reve.com be crawled?
No readable sitemap was found, so crawlers have to discover every page by following links.
A deliberately invalid URL correctly returns HTTP 404, so missing pages will not be indexed.
What tracking does reve.com run?
1 tracking script detected: Google Tag Manager.
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 reve.com look when shared?
4 of 5 social preview tags are set. Missing: og:description.
How are images, fonts and scripts handled?
13 images on the homepage, 11 of them lazy-loaded (85%).
All image references use JPEG, PNG or GIF. WebP or AVIF typically cut image weight substantially at the same visual quality.
The page pulls 0 external stylesheets and 1 external script, with 1 carrying defer or async.
Is reve.com accessible and current?
The page uses 0 landmark elements and 2 ARIA attributes.
No skip-to-content link was found, which keyboard users rely on to bypass navigation.
Can search engines index reve.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.
The homepage carries 1 internal and 0 external links across 0 outside hosts.
Visible text is only 0.3% of the HTML, which indicates the page is assembled in the browser rather than served as content.
How is reve.com delivered?
The HTML is served with Cache-Control: no-cache, private, must-revalidate, max-age=0.
HTTP/3 is advertised via alt-svc, so modern browsers will upgrade to QUIC after the first visit.
A web app manifest is declared, so the site is installable as a progressive web app.
Frequently asked questions
Does reve.com set the usual HTTP security headers?
It sets 2 of 6. The ones not present are: HSTS, X-Content-Type-Options, Referrer-Policy, Permissions-Policy.
Does reve.com allow AI crawlers?
No robots.txt is served, so nothing is disallowed and AI crawlers are free to read the site.
What is reve.com built with?
The homepage exposes these fingerprints: Google Tag Manager. 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 reve.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 →