laroza.one
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafe4 years old
30
laroza.one was registered on 14 Jul 2022 via MarkMonitor, Inc. and the registry expiry is 14 Jul 2027. WHOIS data came from RDAP at https://rdap.nic.one/domain/laroza.one.
laroza.one publishes 2 nameservers. DNSSEC is not signed.
laroza.one has 1 IPv4 address (34.235.250.63). The geolocation database places 34.235.250.63 in Ashburn, United States.
No safety warning was recorded for laroza.one in the checks that ran.
Domain · RDAP/WHOIS
laroza.one was registered on 14 Jul 2022 via MarkMonitor, Inc.. The registry returned 3 status values and 2 nameservers from https://rdap.nic.one/domain/laroza.one.
| Registered | since 14 Jul 2022 |
|---|---|
| Created | 14 July 2022 |
| Updated | 15 October 2025 |
| Expires | 14 July 2027 |
| Registrar | MarkMonitor, Inc. |
| Status | client transfer prohibited, client update prohibited, client delete prohibited |
| Nameservers | ns4.films.org, ns3.films.org |
| DNSSEC | no |
| Source | https://rdap.nic.one/domain/laroza.one |
laroza.one carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.
laroza.one carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.
laroza.one carries the status "client delete prohibited". The registrar has asked the registry to refuse a delete. This is an EPP status on the domain object. It does not say the website is safe, and it does not name the person who registered it.
Nameserver ns4.films.org is published for laroza.one in the registration record from https://rdap.nic.one/domain/laroza.one.
Nameserver ns3.films.org is published for laroza.one in the registration record from https://rdap.nic.one/domain/laroza.one.
DNS
laroza.one has 1 address record, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 34.235.250.63 |
|---|---|
| AAAA | — |
| NS | ns3.films.org, ns4.films.org |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 34.235.250.63 answers for laroza.one at resolver 1.1.1.1:53.
Hosting and geo
laroza.one is placed in Ashburn, United States by the local geolocation database (db-ip).
| Address | 34.235.250.63 |
|---|---|
| Country | United States |
| City | Ashburn |
| Source | db-ip |
SSL/TLS
No TLS certificate was read for laroza.one on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
dial tcp 34.235.250.63:443: i/o timeout
Tech stack
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
On-page checks
The homepage fetch did not return a status code.
| Status | none |
|---|
context deadline exceeded
Security
Family DNS for laroza.one is clear, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | clear |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.
Score breakdown
Availability 10 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 0 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 0 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 0 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.
Safety lists 15 of 15. Points only when the checks ran and came back clean. Unknown is not clean.
Domain age 5 of 5. Five points at one year, two points at 30 days.
Change history
- October 2026: rdap created changed from empty to 2022-07-14T02:30:49Z.
- October 2026: rdap dnssec changed from empty to no.
- October 2026: rdap expires changed from empty to 2027-07-14T02:30:49Z.
- October 2026: rdap nameservers changed from empty to ns3.films.org,ns4.films.org.
- October 2026: rdap registered changed from unknown to yes.
- October 2026: rdap registrar changed from empty to MarkMonitor, Inc..
- October 2026: rdap statuses changed from empty to client delete prohibited,client transfer prohibited,client update prohibited.
- October 2026: rdap updated changed from empty to 2025-10-15T14:45:17Z.
- October 2026: geo city changed from empty to Ashburn.
- October 2026: geo country changed from empty to United States.
Questions
Is laroza.one safe?
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
Who hosts laroza.one?
laroza.one is placed in Ashburn, United States.
When does laroza.one expire?
laroza.one expires on 14 July 2027 according to https://rdap.nic.one/domain/laroza.one.
Who owns laroza.one?
The registry did not return a person or a company for laroza.one. RDAP often redacts the registrant. The registrar on file is MarkMonitor, Inc..
Sources
- RDAP source https://rdap.nic.one/domain/laroza.one at 2026-10-30T15:00:40Z
- DNS source 1.1.1.1:53 at 2026-10-30T15:00:40Z
- TLS source tls:443 at 2026-10-30T15:00:40Z
- HTTP source https://laroza.one/ at 2026-10-30T15:00:40Z
- Tech source not available at 2026-10-30T15:00:40Z
- Geo source db-ip at 2026-10-30T15:00:40Z
- Safety source family DNS and local lists at 2026-10-30T15:00:40Z
Related reports
No other indexable reports share this TLD, host, or registrar yet.
Owner of this site?
Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.
How to read this report
The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.