rom.com is a live website, registered in 1995, served from Milton Keynes, United Kingdom. It has a valid HTTPS certificate, 3 of 6 common security headers.
What is rom.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:
- domain ×6
- safenames ×4
- registered ×2
- security ×2
- management ×2
Does rom.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 rom.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 82% of them (median 443ms) |
|---|---|
| Security headers | More than 72% of them |
| Domain age | Older than 86% of them |
Related domains in this index
Other analysed domains served from the same country:
When was rom.com registered?
rom.com was registered on 20 April 1995, which makes it about 31 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 SafeNames Ltd..
Registration runs until 21 April 2028.
The domain carries 3 registry locks, which blocks unauthorised transfer or deletion.
| Registered | 20 April 1995 |
|---|---|
| Expires | 21 April 2028 |
| Registrar | SafeNames Ltd. |
| Registry status | client delete prohibited, client transfer prohibited, client update prohibited |
Where is rom.com hosted?
The first address resolves to infrastructure in Milton Keynes, United Kingdom.
The network is operated by Safenames Ltd (AS60819 Safenames Ltd.).
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 rom.com running on?
No platform, framework or analytics fingerprints were found in the homepage markup of rom.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
HTTPS.
At 103ms to first byte this response is fast for a homepage measured from a single European location.
At 9KB the HTML is unusually small, which typically means the page builds itself client-side after load.
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 | 9,106 bytes |
| Declared language | en |
| Mobile viewport | declared |
What does the homepage say about itself?
The title is 30 characters, inside the range that displays without truncation.
There is no meta description, so the snippet shown in search results is assembled by the search engine from whatever text it considers relevant.
| Title | Domain Registered at Safenames (30 chars) |
|---|---|
| Meta description | — none — (0 chars) |
| H1 | This domain is registered with Safenames (1 on the page) |
| Canonical | not set |
| Open Graph title | not set |
| Headings / images | 0 H2s, 0 images (0 without alt text) |
Is rom.com served over a valid certificate?
The HTTPS certificate is issued by Let's Encrypt and is
valid until 2026-12-14, which is 70 days from the date of this check. It covers
2 hostnames.
- rom.com
- www.rom.com
The certificate has 70 days left to run.
It covers 2 hostnames, so it was issued for this site specifically.
Let's Encrypt certificates are free and run on 90-day terms, so this site is almost certainly renewing automatically.
Which security headers does it set?
3 of 6 are set (Content Security Policy, X-Content-Type-Options, Referrer-Policy). Absent: HSTS, X-Frame-Options, 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'; style-src 'unsafe-inline'; base-uri 'none'; form-action 'none' |
| X-Content-Type-Options | yes | nosniff |
| X-Frame-Options | no | — |
| Referrer-Policy | yes | strict-origin-when-cross-origin |
| Permissions-Policy | no | — |
How is DNS configured for rom.com?
| IP addresses | 217.19.248.132 |
|---|---|
| Reverse DNS | redirect.idp365.net |
| Name servers | dns1.idp365.net, dns2.idp365.net, dns3.idp365.net |
| Mail (MX) | mail.idp365.net (pri 10) |
| SPF | not published |
| TXT records | 1 |
rom.com resolves to a single address, so there is no DNS-level redundancy.
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 redirect.idp365.net, which usually names the hosting provider.
Who runs DNS and mail for rom.com?
Mail exchangers point at hosts that do not match any major provider, which usually means self-hosted or niche-provider mail.
No AAAA records are published, so the site is reachable over IPv4 only.
Can rom.com be spoofed in email?
DMARC is set to reject, the strictest setting: mail that fails authentication is refused outright. This is the configuration that actually stops domain spoofing.
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 rom.com load from third parties?
The homepage loads no resources from third-party hosts at all, which is rare and means visiting it tells no other company that you did.
No cookies are set on first load.
Does rom.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 rom.com and www.rom.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 rom.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 rom.com run?
No analytics or advertising trackers were detected on the homepage of rom.com, which is unusual for a commercial site.
How does rom.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?
The page pulls 0 external stylesheets and 0 external scripts, with 0 carrying defer or async.
Is rom.com accessible and current?
The page uses 1 landmark element and 1 ARIA attribute.
No skip-to-content link was found, which keyboard users rely on to bypass navigation.
Can search engines index rom.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 1 external link across 1 outside host.
Visible text makes up 6.6% of the HTML.
How is rom.com delivered?
The HTML is served with Cache-Control: max-age=300.
No favicon is declared in the markup.
The TLS certificate also covers 1 subdomain: www.rom.com.
- www.rom.com
Frequently asked questions
Does rom.com set the usual HTTP security headers?
It sets 3 of 6. The ones not present are: HSTS, X-Frame-Options, Permissions-Policy.
Does rom.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 rom.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 →