sniffip.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafe13 years old
30
sniffip.com was registered on 3 Dec 2012 via OVH sas and the registry expiry is 3 Dec 2026. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/sniffip.com.
sniffip.com publishes 13 nameservers. DNSSEC is not signed.
sniffip.com has 1 IPv4 address (178.32.54.112). The geolocation database places 178.32.54.112 in Paris, France.
No safety warning was recorded for sniffip.com in the checks that ran.
Domain · RDAP/WHOIS
sniffip.com was registered on 3 Dec 2012 via OVH sas. The registry returned 2 status values and 4 nameservers from https://rdap.verisign.com/com/v1/domain/sniffip.com.
| Registered | since 3 Dec 2012 |
|---|---|
| Created | 3 December 2012 |
| Updated | 4 December 2025 |
| Expires | 3 December 2026 |
| Registrar | OVH sas |
| Status | client delete prohibited, client transfer prohibited |
| Nameservers | ns1.cloudns.net, ns2.cloudns.net, ns3.cloudns.net, ns4.cloudns.net |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/sniffip.com |
sniffip.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.
sniffip.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 ns1.cloudns.net is published for sniffip.com in the registration record from https://rdap.verisign.com/com/v1/domain/sniffip.com.
Nameserver ns2.cloudns.net is published for sniffip.com in the registration record from https://rdap.verisign.com/com/v1/domain/sniffip.com.
Nameserver ns3.cloudns.net is published for sniffip.com in the registration record from https://rdap.verisign.com/com/v1/domain/sniffip.com.
Nameserver ns4.cloudns.net is published for sniffip.com in the registration record from https://rdap.verisign.com/com/v1/domain/sniffip.com.
DNS
sniffip.com has 1 address record, 1 mail exchanger and 13 nameservers, measured at 1.1.1.1:53.
| A | 178.32.54.112 |
|---|---|
| AAAA | — |
| NS | ns1.cloudns.net, ns2.cloudns.net, ns3.cloudns.net, ns4.cloudns.net, pns1.cloudns.net, pns2.cloudns.net, pns3.cloudns.net, pns4.cloudns.net, pns5.cloudns.net, pns6.cloudns.net, pns7.cloudns.net, pns8.cloudns.net, pns9.cloudns.net |
| MX | mail.sniffip.com (10) |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 178.32.54.112 answers for sniffip.com at resolver 1.1.1.1:53.
Mail exchanger mail.sniffip.com has preference 10.
A random label under sniffip.com also resolved, which means wildcard DNS is on.
Hosting and geo
sniffip.com is placed in Paris, France by the local geolocation database (db-ip).
| Address | 178.32.54.112 |
|---|---|
| Country | France |
| City | Paris |
| Source | db-ip |
SSL/TLS
No TLS certificate was read for sniffip.com on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
dial tcp 178.32.54.112: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 sniffip.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 Paris.
- October 2026: geo country changed from empty to France.
Questions
Is sniffip.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 sniffip.com?
sniffip.com is placed in Paris, France.
When does sniffip.com expire?
sniffip.com expires on 3 December 2026 according to https://rdap.verisign.com/com/v1/domain/sniffip.com.
Who owns sniffip.com?
The registry did not return a person or a company for sniffip.com. RDAP often redacts the registrant. The registrar on file is OVH sas.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/sniffip.com at 2026-10-30T14:14:39Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:14:39Z
- TLS source tls:443 at 2026-10-30T14:14:39Z
- HTTP source https://sniffip.com/ at 2026-10-30T14:14:39Z
- Tech source not available at 2026-10-30T14:14:39Z
- Geo source db-ip at 2026-10-30T14:14:39Z
- Safety source family DNS and local lists at 2026-10-30T14:14: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.