odessafile.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 307SafeSSL: 64 days left23 years old
80
odessafile.com was registered on 24 Dec 2002 via GoDaddy.com, LLC and the registry expiry is 24 Dec 2026. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/odessafile.com.
odessafile.com publishes 2 nameservers. DNSSEC is not signed.
odessafile.com has 1 IPv4 address (192.124.249.154). The geolocation database places 192.124.249.154 in Menifee, United States.
The TLS certificate from GoDaddy TLS Intermediate CA DV - R1v1 is valid and has 64 days left (TLS 1.3). The homepage answered HTTP 307.
Tech detection named HTTP/3 and Sucuri. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for odessafile.com in the checks that ran.
Domain · RDAP/WHOIS
odessafile.com was registered on 24 Dec 2002 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/odessafile.com.
| Registered | since 24 Dec 2002 |
|---|---|
| Created | 24 December 2002 |
| Updated | 24 December 2025 |
| Expires | 24 December 2026 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | ns3.secureserver.net, ns4.secureserver.net |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/odessafile.com |
odessafile.com 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.
odessafile.com carries the status "client renew prohibited". The registrar has asked the registry to refuse a renewal. The expiry date still stands until a different status is set.
odessafile.com 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.
odessafile.com 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.
Nameserver ns3.secureserver.net is published for odessafile.com in the registration record from https://rdap.verisign.com/com/v1/domain/odessafile.com.
Nameserver ns4.secureserver.net is published for odessafile.com in the registration record from https://rdap.verisign.com/com/v1/domain/odessafile.com.
DNS
odessafile.com has 1 address record, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 192.124.249.154 |
|---|---|
| AAAA | — |
| NS | ns3.secureserver.net, ns4.secureserver.net |
| MX | odessafile-com.mail.protection.outlook.com (0) Microsoft 365 |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at odessafile.com is "v=spf1 include:secureserver.net -all".
IPv4 address 192.124.249.154 answers for odessafile.com at resolver 1.1.1.1:53.
Mail exchanger odessafile-com.mail.protection.outlook.com has preference 0. The host is recognised as Microsoft 365.
Hosting and geo
odessafile.com is placed in Menifee, United States by the local geolocation database (db-ip).
| Address | 192.124.249.154 |
|---|---|
| Country | United States |
| City | Menifee |
| Source | db-ip |
SSL/TLS
The certificate for odessafile.com is valid, with 64 days left and 2 subject alternative names. Source: tls:443.
| Issuer | GoDaddy TLS Intermediate CA DV - R1v1 |
|---|---|
| Subject | odessafile.com |
| Valid from | 6 October 2026 |
| Valid until | 4 January 2027 |
| Days left | 64 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: odessafile.com, www.odessafile.com.
Tech stack
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
- HTTP/3 · Miscellaneous
- Sucuri · CDN, Security
HTTP/3 is filed under Miscellaneous.
Sucuri is filed under CDN, Security.
On-page checks
The homepage returned HTTP 307 in 4 ms. The target title is 27 characters and the page has 0 H1 headings.
| Status | 307 |
|---|---|
| TTFB | 4 ms |
| Title length | 27 yes |
| Quoted title | "You are being redirected..." |
| Meta description | none no |
| H1 count | 0 |
| HSTS | no no |
| CSP | yes |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 0 |
| Images | 0 |
| Favicon | no |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Security
Family DNS for odessafile.com 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 | yes |
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 25 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 20 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 5 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 10 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: http status_class changed from 2xx to 3xx.
- October 2026: tech removed Google Analytics.
- October 2026: geo city changed from empty to Menifee.
- October 2026: geo country changed from empty to United States.
Questions
Is odessafile.com 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 odessafile.com?
odessafile.com is placed in Menifee, United States.
When does odessafile.com expire?
odessafile.com expires on 24 December 2026 according to https://rdap.verisign.com/com/v1/domain/odessafile.com.
Who owns odessafile.com?
The registry did not return a person or a company for odessafile.com. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/odessafile.com at 2026-10-30T14:07:39Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:07:39Z
- TLS source tls:443 at 2026-10-30T14:07:39Z
- HTTP source https://odessafile.com/ at 2026-10-30T14:07:39Z
- Tech source wappalyzergo at 2026-10-30T14:07:39Z
- Geo source db-ip at 2026-10-30T14:07:39Z
- Safety source family DNS and local lists at 2026-10-30T14:07:39Z
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.