slushy.com describes itself as "Swipe through trending videos, message creators directly, and explore exclusive short-form content on Slushy's interactive feed.". It is built on Next.js, registered in 2005, served from Frankfurt am Main, Germany. It has a valid HTTPS certificate, 0 of 6 common security headers.
Does slushy.com publish the usual trust pages?
Found: about, contact, terms. Not found at the usual addresses:
privacy.
These were checked at conventional paths only, so a site using different URLs may
publish them elsewhere.
How does slushy.com compare with other domains analysed here?
Measured against the 77 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 66% of them (median 496ms) |
|---|---|
| Security headers | More than 0% of them |
| Domain age | Older than 53% of them |
Related domains in this index
Analysed domains sharing the same network (AS16509 Amazon.com, Inc.):
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:
Other analysed domains served from the same country:
When was slushy.com registered?
slushy.com was registered on 16 February 2005, which makes it about 21 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 Amazon Registrar, Inc..
Registration runs until 16 February 2027.
The domain carries 1 registry lock, which blocks unauthorised transfer or deletion.
| Registered | 16 February 2005 |
|---|---|
| Expires | 16 February 2027 |
| Registrar | Amazon Registrar, Inc. |
| Registry status | client transfer prohibited |
Where is slushy.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 slushy.com running on?
slushy.com exposes 1 identifiable technology: Next.js.
The build output indicates a server-rendered JavaScript framework, which means the HTML served to crawlers is generated ahead of time rather than assembled in the browser.
- Next.js
How does the homepage respond?
The server answered with HTTP 200 over
HTTPS.
At 392ms to first byte this response is unremarkable for a homepage measured from a single European location.
At 12KB the HTML is unusually small, which typically means the page builds itself client-side after load.
The HTML is compressed with gzip.
| Server header | not disclosed |
|---|---|
| Compression | gzip |
| Page size | 12,148 bytes |
| Declared language | not declared |
| Mobile viewport | declared |
What does the homepage say about itself?
The title is 35 characters, inside the range that displays without truncation.
A meta description of 128 characters is present.
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 | Watch & Chat with Creators | Slushy (35 chars) |
|---|---|
| Meta description | Swipe through trending videos, message creators directly, and explore exclusive short-form content on Slushy's interactive feed. (128 chars) |
| H1 | — none — (0 on the page) |
| Canonical | https://www.slushy.com/ |
| Open Graph title | Watch & Chat with Creators | Slushy Feed |
| Headings / images | 0 H2s, 0 images (0 without alt text) |
Is slushy.com served over a valid certificate?
The HTTPS certificate is issued by Amazon and is
valid until 2027-04-08, which is 185 days from the date of this check. It covers
2 hostnames.
- *.slushy.com
- slushy.com
The certificate has 185 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 slushy.com?
| IP addresses | 18.245.86.63, 18.245.86.36, 18.245.86.110, 18.245.86.52 |
|---|---|
| Reverse DNS | server-18-245-86-63.fra60.r.cloudfront.net, server-18-245-86-36.fra60.r.cloudfront.net |
| Name servers | ns-488.awsdns-61.com, ns-607.awsdns-11.net, ns-1354.awsdns-41.org, ns-1896.awsdns-45.co.uk |
| Mail (MX) | alt4.aspmx.l.google.com (pri 10), ba4q3db6rghmyt4ajlby5mvkedzk2lvyjeqylibfu42f5twlf3ta.mx-verification.google.com (pri 15), alt1.aspmx.l.google.com (pri 5), alt2.aspmx.l.google.com (pri 5), aspmx.l.google.com (pri 1), alt3.aspmx.l.google.com (pri 10) |
| SPF | v=spf1 include:_spf.google.com include:amazonses.com ~all |
| TXT records | 5 |
slushy.com resolves to 4 addresses, which indicates load balancing or a CDN rather than a single origin server.
Mail is handled by 6 exchangers.
An SPF record is published, giving receiving servers a rule for which hosts may send as this domain.
Reverse DNS resolves to server-18-245-86-63.fra60.r.cloudfront.net, server-18-245-86-36.fra60.r.cloudfront.net, which usually names the hosting provider.
Who runs DNS and mail for slushy.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 slushy.com?
2 of 2 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.
Can slushy.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 3,622 bytes and names
7 user-agent groups.
It does not blanket-disallow general crawlers.
Sitemaps declared:
- https://www.slushy.com/sitemap.xml
- https://www.slushy.com/server-sitemap.xml
AI crawler policy
| Crawler | Policy |
|---|---|
| gptbot | allowed |
| claudebot | allowed |
| perplexitybot | allowed |
| google-extended | allowed |
| ccbot | allowed |
2 sitemaps are declared in robots.txt, which gives crawlers a direct list of URLs.
Named AI crawlers are explicitly allowed (gptbot, claudebot, perplexitybot, google-extended, ccbot).
What structured data does the homepage publish?
- Organization
- WebSite
- SearchAction
- WebApplication
- Offer
The homepage publishes 5 structured data types: Organization, WebSite, SearchAction, WebApplication, Offer.
What does slushy.com load from third parties?
The homepage pulls resources from 2 third-party hosts (cmp.osano.com, freditorsuberra.com). Each one sees the visitor IP and user agent on every page load.
No cookies are set on first load.
The page links or refers to X/Twitter.
Does slushy.com settle on one address?
Plain HTTP redirects to HTTPS, so visitors who type the bare address still land on the secure version.
Both slushy.com and www.slushy.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 slushy.com be crawled?
A sitemap index is served at https://www.slushy.com/sitemap.xml listing 2 entries.
A deliberately invalid URL correctly returns HTTP 404, so missing pages will not be indexed.
What tracking does slushy.com run?
No analytics or advertising trackers were detected on the homepage of slushy.com, which is unusual for a commercial site.
How does slushy.com look when shared?
All five social preview tags are present, so links shared to social platforms and chat apps will render with a title, description and image.
The page declares 1 hreflang alternate (x-default), so it targets more than one language or region.
How are images, fonts and scripts handled?
The page pulls 1 external stylesheet and 29 external scripts, with 28 carrying defer or async.
Responses carry Amazon CloudFront and edge cache edge headers, so content is served from a CDN rather than straight from the origin.
Is slushy.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 slushy.com?
Nothing on the homepage prevents indexing: no noindex is set in the robots meta tag or the X-Robots-Tag header.
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 slushy.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.
A web app manifest is declared, so the site is installable as a progressive web app.
Frequently asked questions
Does slushy.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 slushy.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 slushy.com built with?
The homepage exposes these fingerprints: Next.js. 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 slushy.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 →