omnitalk.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafe29 years oldTranco #671781
30
omnitalk.com was registered on 31 Jul 1997 via Network Solutions, LLC and the registry expiry is 30 Jul 2035. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/omnitalk.com.
omnitalk.com publishes 4 nameservers. DNSSEC is not signed.
omnitalk.com has 1 IPv4 address (74.208.236.73). The geolocation database places 74.208.236.73 in Kansas City, United States.
No safety warning was recorded for omnitalk.com in the checks that ran.
Domain · RDAP/WHOIS
omnitalk.com was registered on 31 Jul 1997 via Network Solutions, LLC. The registry returned 1 status value and 4 nameservers from https://rdap.verisign.com/com/v1/domain/omnitalk.com.
| Registered | since 31 Jul 1997 |
|---|---|
| Created | 31 July 1997 |
| Updated | 31 July 2025 |
| Expires | 30 July 2035 |
| Registrar | Network Solutions, LLC |
| Status | client transfer prohibited |
| Nameservers | ns-us.1and1-dns.com, ns-us.1and1-dns.de, ns-us.1and1-dns.org, ns-us.1and1-dns.us |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/omnitalk.com |
omnitalk.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.
Nameserver ns-us.1and1-dns.com is published for omnitalk.com in the registration record from https://rdap.verisign.com/com/v1/domain/omnitalk.com.
Nameserver ns-us.1and1-dns.de is published for omnitalk.com in the registration record from https://rdap.verisign.com/com/v1/domain/omnitalk.com.
Nameserver ns-us.1and1-dns.org is published for omnitalk.com in the registration record from https://rdap.verisign.com/com/v1/domain/omnitalk.com.
Nameserver ns-us.1and1-dns.us is published for omnitalk.com in the registration record from https://rdap.verisign.com/com/v1/domain/omnitalk.com.
DNS
omnitalk.com has 1 address record, 2 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 74.208.236.73 |
|---|---|
| AAAA | — |
| NS | ns-us.1and1-dns.com, ns-us.1and1-dns.de, ns-us.1and1-dns.org, ns-us.1and1-dns.us |
| MX | mx00.1and1.com (10), mx01.1and1.com (11) |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 74.208.236.73 answers for omnitalk.com at resolver 1.1.1.1:53.
Mail exchanger mx00.1and1.com has preference 10.
Mail exchanger mx01.1and1.com has preference 11.
Hosting and geo
omnitalk.com is placed in Kansas City, United States by the local geolocation database (db-ip).
| Address | 74.208.236.73 |
|---|---|
| Country | United States |
| City | Kansas City |
| Source | db-ip |
SSL/TLS
No TLS certificate was read for omnitalk.com on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
remote error: tls: internal error
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 |
|---|
Get "https://omnitalk.com/": remote error: tls: internal error
Security
Family DNS for omnitalk.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 | 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: geo city changed from empty to Kansas City.
- October 2026: geo country changed from empty to United States.
Questions
Is omnitalk.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 omnitalk.com?
omnitalk.com is placed in Kansas City, United States.
When does omnitalk.com expire?
omnitalk.com expires on 30 July 2035 according to https://rdap.verisign.com/com/v1/domain/omnitalk.com.
Who owns omnitalk.com?
The registry did not return a person or a company for omnitalk.com. RDAP often redacts the registrant. The registrar on file is Network Solutions, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/omnitalk.com at 2026-10-30T14:07:52Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:07:52Z
- TLS source tls:443 at 2026-10-30T14:07:52Z
- HTTP source https://omnitalk.com/ at 2026-10-30T14:07:52Z
- Tech source not available at 2026-10-30T14:07:52Z
- Geo source db-ip at 2026-10-30T14:07:52Z
- Safety source family DNS and local lists at 2026-10-30T14:07:52Z
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.