Article
xlove.com — domain analysis
xlove.com describes itself as "xlove.com: watch adult live cams and sexy live shows. Performers online and a simple, discreet live experience.". It was registered in 1999, served from Toronto, Canada.…
xlove.com describes itself as "xlove.com: watch adult live cams and sexy live shows. Performers online and a simple, discreet live experience.". It was registered in 1999, served from Toronto, Canada. It has a valid HTTPS certificate, 3 of 6 common security headers.
What is xlove.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:
- rsaquo ×81
- private ×37
- xlove ×31
- times ×29
- show ×29
- model ×28
- free ×25
- sign ×25
- 0sec ×25
- users ×20
Does xlove.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 xlove.com compare with other domains analysed here?
Measured against the 79 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 41% of them (median 419ms) |
|---|---|
| Security headers | More than 79% of them |
| Domain age | Older than 67% of them |
Related domains in this index
Analysed domains sharing the same network (AS13335 Cloudflare, 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 xlove.com registered?
xlove.com was registered on 3 February 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 3 February 2027.
The domain carries 1 registry lock, which blocks unauthorised transfer or deletion.
| Registered | 3 February 1999 |
|---|---|
| Expires | 3 February 2027 |
| Registrar | Network Solutions, LLC |
| Registry status | client transfer prohibited |
Where is xlove.com hosted?
The first address resolves to infrastructure in Toronto, Canada.
The network is operated by CloudFlare, Inc. (AS13335 Cloudflare, 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 xlove.com running on?
xlove.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 533ms to first byte this response is unremarkable for a homepage measured from a single European location.
The HTML weighs 318KB, which is ordinary for a homepage.
The HTML is compressed with gzip.
| Server header | cloudflare |
|---|---|
| Compression | gzip |
| Page size | 325,179 bytes |
| Declared language | en |
| Mobile viewport | declared |
What does the homepage say about itself?
The title is 47 characters, inside the range that displays without truncation.
A meta description of 111 characters is present.
There are 2 H1 headings. One is conventional; several dilute the signal about what the page is primarily about.
All 64 images on the homepage have alt attributes.
| Title | xlove.com – Adult live cams and sexy live shows (47 chars) |
|---|---|
| Meta description | xlove.com: watch adult live cams and sexy live shows. Performers online and a simple, discreet live experience. (111 chars) |
| H1 | About xlove.com (2 on the page) |
| Canonical | https://www.xlove.com/en/ |
| Open Graph title | not set |
| Headings / images | 18 H2s, 64 images (0 without alt text) |
Is xlove.com served over a valid certificate?
The HTTPS certificate is issued by Google Trust Services and is
valid until 2026-11-14, which is 39 days from the date of this check. It covers
2 hostnames.
- xlove.com
- *.xlove.com
The certificate has 39 days left to run.
It covers 2 hostnames, so it was issued for this site specifically.
Which security headers does it set?
3 of 6 are set (HSTS, Content Security Policy, X-Frame-Options). Absent: X-Content-Type-Options, Referrer-Policy, Permissions-Policy.
| Header | Set | Value |
|---|---|---|
| HSTS | yes | max-age=18144000 |
| Content Security Policy | yes | script-src 'self' *.wlresources.com *.acwebconnecting.com 'sha256-CCK/xSkL7d3chQiFuPZVP/tXpFacyHTeh5K40SIReN4=' https:// |
| X-Content-Type-Options | no | — |
| X-Frame-Options | yes | DENY |
| Referrer-Policy | no | — |
| Permissions-Policy | no | — |
How is DNS configured for xlove.com?
| IP addresses | 188.114.97.9, 188.114.96.9, 2a06:98c1:3121::9, 2a06:98c1:3120::9 |
|---|---|
| Reverse DNS | 188.114.97.9, 188.114.96.9 |
| Name servers | fay.ns.cloudflare.com, rex.ns.cloudflare.com |
| Mail (MX) | mail.xlove.com (pri 10) |
| SPF | not published |
| TXT records | 0 |
xlove.com resolves to 4 addresses, which indicates load balancing or a CDN rather than a single origin server.
Mail is handled by 1 exchanger.
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 188.114.97.9, 188.114.96.9, which usually names the hosting provider.
Who runs DNS and mail for xlove.com?
DNS is operated by Cloudflare rather than self-hosted name servers.
Mail exchangers point at hosts that do not match any major provider, which usually means self-hosted or niche-provider mail.
The domain publishes AAAA records and accepts connections over IPv6.
What else is worth noting about xlove.com?
4 of 4 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 xlove.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?
robots.txt is 818 bytes and names
23 user-agent groups.
It does not blanket-disallow general crawlers.
Sitemaps declared:
- https://xlove.com/sitemap.xml
AI crawler policy
| Crawler | Policy |
|---|---|
| gptbot | allowed |
| claudebot | allowed |
| perplexitybot | blocked |
| anthropic-ai | allowed |
1 sitemap is declared in robots.txt, which gives crawlers a direct list of URLs.
AI crawler policy is selective: perplexitybot blocked, gptbot, claudebot, anthropic-ai allowed.
What structured data does the homepage publish?
- WebSite
- Organization
- Brand
- ContactPoint
The homepage publishes 4 structured data types: WebSite, Organization, Brand, ContactPoint.
What does xlove.com load from third parties?
The homepage pulls resources from 4 third-party hosts (img1.wlresources.com, medianew.wlresources.com, s1.wlresources.com, spcdn1.wlresources.com). Each one sees the visitor IP and user agent on every page load.
3 cookies are set before any interaction (csrf, PHPSESSID, csrf).
The page links or refers to X/Twitter, Facebook, Instagram, YouTube.
| Cookie | Secure | HttpOnly | SameSite |
|---|---|---|---|
| csrf | yes | yes | lax |
| PHPSESSID | yes | yes | lax |
| csrf | yes | yes | lax |
Does xlove.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, so the site settles on one canonical hostname.
How easily can xlove.com be crawled?
A sitemap index is served at https://xlove.com/sitemap.xml listing 182 entries.
The most recent lastmod date is 2026-10-04.
A deliberately invalid URL correctly returns HTTP 404, so missing pages will not be indexed.
What tracking does xlove.com run?
No analytics or advertising trackers were detected on the homepage of xlove.com, which is unusual for a commercial site.
How does xlove.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.
The page declares 8 hreflang alternates (de, en, x-default, es, fr, it, nl, pt), so it targets more than one language or region.
How are images, fonts and scripts handled?
64 images on the homepage, 22 of them lazy-loaded (34%).
All image references use JPEG, PNG or GIF. WebP or AVIF typically cut image weight substantially at the same visual quality.
No srcset attributes are used, so every device is served the same image size regardless of screen.
The page pulls 3 external stylesheets and 4 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 xlove.com accessible and current?
The page uses 1 landmark element and 76 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.
There are 52 form inputs but only 19 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 xlove.com?
Nothing on the homepage prevents indexing: no noindex is set in the robots meta tag or the X-Robots-Tag header.
The homepage carries 185 internal and 8 external links across 4 outside hosts.
Visible text makes up 6.7% of the HTML.
How is xlove.com delivered?
The HTML is served with Cache-Control: no-store, no-cache, must-revalidate.
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 xlove.com set the usual HTTP security headers?
It sets 3 of 6. The ones not present are: X-Content-Type-Options, Referrer-Policy, Permissions-Policy.
Does xlove.com allow AI crawlers?
No — robots.txt blocks perplexitybot.
What is xlove.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 xlove.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 →