Article
romeo.com — domain analysis
romeo.com describes itself as "The top choice for gay, bi and trans dating. Find dates, make friends and fall in love on the ROMEO website, iOS or Android app. Happy…
romeo.com describes itself as "The top choice for gay, bi and trans dating. Find dates, make friends and fall in love on the ROMEO website, iOS or Android app. Happy dating!". It was registered in 1998, served from Toronto, Canada. It has a valid HTTPS certificate, 5 of 6 common security headers, 1 tracking script.
What is romeo.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:
- romeo ×3
- browser ×3
Does romeo.com publish the usual trust pages?
All four of the pages a established business normally publishes were found:
about, contact, privacy and terms.
These were checked at conventional paths only, so a site using different URLs may
publish them elsewhere.
How does romeo.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 70% of them (median 419ms) |
|---|---|
| Security headers | More than 93% of them |
| Domain age | Older than 74% 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:
- alamy.com
- anime.com
- compramostucoche.com
- globoesporte.com
- indigo.com
- merdeka.com
- playlistpush.com
- tunota.com
Other analysed domains served from the same country:
When was romeo.com registered?
romeo.com was registered on 10 July 1998, which makes it about 28 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 InterNetX GmbH.
Registration runs until 9 July 2027.
The domain carries 1 registry lock, which blocks unauthorised transfer or deletion.
| Registered | 10 July 1998 |
|---|---|
| Expires | 9 July 2027 |
| Registrar | InterNetX GmbH |
| Registry status | client transfer prohibited |
Where is romeo.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 romeo.com running on?
romeo.com exposes 2 identifiable technologies: Cloudflare, Google Tag Manager.
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.
Visitor tracking is present (Google Tag Manager), so this homepage is not cookie-free.
- Cloudflare
- Google Tag Manager
How does the homepage respond?
The server answered with HTTP 200 over
HTTPS.
At 158ms to first byte this response is fast for a homepage measured from a single European location.
The HTML weighs 69KB, which is ordinary for a homepage.
The HTML is compressed with gzip.
| Server header | cloudflare |
|---|---|
| Compression | gzip |
| Page size | 70,269 bytes |
| Declared language | not declared |
| Mobile viewport | declared |
What does the homepage say about itself?
The title is 64 characters, inside the range that displays without truncation.
A meta description of 142 characters is present.
No H1 heading was found, so the page offers no single top-level statement of what it is.
All 1 images on the homepage have alt attributes.
The html element declares no lang attribute, which removes a signal both screen readers and translation tools rely on.
| Title | ROMEO | Gay, Bi and Trans Dating and Chat | Dates. Friends. Love (64 chars) |
|---|---|
| Meta description | The top choice for gay, bi and trans dating. Find dates, make friends and fall in love on the ROMEO website, iOS or Android app. Happy dating! (142 chars) |
| H1 | — none — (0 on the page) |
| Canonical | not set |
| Open Graph title | ROMEO | Gay, Bi and Trans Dating and Chat |
| Headings / images | 0 H2s, 1 images (0 without alt text) |
Is romeo.com served over a valid certificate?
The HTTPS certificate is issued by Google Trust Services and is
valid until 2026-11-25, which is 51 days from the date of this check. It covers
2 hostnames.
- romeo.com
- *.romeo.com
The certificate has 51 days left to run.
It covers 2 hostnames, so it was issued for this site specifically.
Which security headers does it set?
5 of 6 are set (HSTS, Content Security Policy, X-Content-Type-Options, X-Frame-Options, Referrer-Policy). Absent: Permissions-Policy.
| Header | Set | Value |
|---|---|---|
| HSTS | yes | max-age=31536000; includeSubDomains; preload |
| Content Security Policy | yes | base-uri 'self' *.nr-data.net; child-src blob:; connect-src 'self' wss://*.planetromeo.com wss://*.romeo.com wss://*.hun |
| X-Content-Type-Options | yes | nosniff |
| X-Frame-Options | yes | SAMEORIGIN |
| Referrer-Policy | yes | strict-origin-when-cross-origin |
| Permissions-Policy | no | — |
How is DNS configured for romeo.com?
| IP addresses | 104.18.22.69, 104.18.23.69 |
|---|---|
| Reverse DNS | 104.18.22.69, 104.18.23.69 |
| Name servers | josh.ns.cloudflare.com, zara.ns.cloudflare.com |
| Mail (MX) | alt3.aspmx.l.google.com (pri 10), alt4.aspmx.l.google.com (pri 10), alt1.aspmx.l.google.com (pri 5), alt2.aspmx.l.google.com (pri 5), aspmx.l.google.com (pri 1) |
| SPF | v=spf1 mx ip4:83.98.143.0/24 ip4:185.230.103.248/24 include:_spf.google.com include:mail.zendesk.com -all |
| TXT records | 4 |
romeo.com resolves to 2 addresses, which indicates load balancing or a CDN rather than a single origin server.
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 104.18.22.69, 104.18.23.69, which usually names the hosting provider.
Who runs DNS and mail for romeo.com?
DNS is operated by Cloudflare 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 romeo.com?
All 1 externally hosted scripts carry subresource integrity hashes, so a compromised CDN could not silently swap them.
Can romeo.com be spoofed in email?
DMARC is set to quarantine, so mail failing authentication is sent to spam rather than the inbox.
CAA records restrict certificate issuance to 6 named authorities (issuewild ssl.com, iodef mailto:ssladmin@planetromeo.com, issue amazon.com, issue comodoca.com), so no other CA should be able to issue 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 else does romeo.com publish?
A security.txt file is published, giving security researchers a documented way to report vulnerabilities. Very few sites bother.
An ads.txt file is published with 5 entries, which means the site sells programmatic advertising and has declared who may resell its inventory.
What does robots.txt allow?
robots.txt is 73 bytes and names
2 user-agent groups.
It does not blanket-disallow general crawlers.
No sitemap is declared in robots.txt.
AI crawler policy
| Crawler | Policy |
|---|---|
| gptbot | blocked |
No sitemap is declared in robots.txt, so crawlers must discover pages by following links.
Every named AI crawler is blocked (gptbot). This domain has opted out of AI training and AI answer surfaces wholesale.
What structured data does the homepage publish?
No JSON-LD or microdata was found on the homepage.
What does romeo.com load from third parties?
The homepage pulls resources from 2 third-party hosts (static.cloudflareinsights.com, use.typekit.net). 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, GitHub.
Does romeo.com settle on one address?
Plain HTTP redirects to HTTPS, so visitors who type the bare address still land on the secure version.
Both romeo.com and www.romeo.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 romeo.com be crawled?
A sitemap index is served at https://romeo.com/sitemap.xml listing 3 entries.
The most recent lastmod date in it is 2017-05-31, around 3459 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 romeo.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 romeo.com look when shared?
4 of 5 social preview tags are set. Missing: twitter:card.
How are images, fonts and scripts handled?
1 image on the homepage, 0 of them lazy-loaded (0%).
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 4 external stylesheets and 6 external scripts, with 5 carrying defer or async.
No preconnect hints are declared despite third-party scripts being present, so each new origin pays a full connection setup before it can deliver anything.
Responses carry Cloudflare edge headers, so content is served from a CDN rather than straight from the origin.
Is romeo.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 romeo.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 0 internal and 5 external links across 5 outside hosts.
Visible text is only 0.5% of the HTML, which indicates the page is assembled in the browser rather than served as content.
How is romeo.com delivered?
The HTML is served with Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0.
A web app manifest is declared, so the site is installable as a progressive web app.
Frequently asked questions
Does romeo.com set the usual HTTP security headers?
It sets 5 of 6. The ones not present are: Permissions-Policy.
Does romeo.com allow AI crawlers?
No — robots.txt blocks gptbot.
What is romeo.com built with?
The homepage exposes these fingerprints: Cloudflare, 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 romeo.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 →