dirtypornvids.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineFamily DNS blocked14 years oldTranco #676426
25
dirtypornvids.com was registered on 7 Oct 2012 via Danesco Trading Ltd. and the registry expiry is 7 Oct 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/dirtypornvids.com.
dirtypornvids.com publishes 2 nameservers. DNSSEC is not signed.
dirtypornvids.com has 1 IPv4 address (88.208.55.232) and 1 IPv6 address (2a02:b4a:1::5727:1). The geolocation database places 88.208.55.232 in Amsterdam, The Netherlands.
Domain · RDAP/WHOIS
dirtypornvids.com was registered on 7 Oct 2012 via Danesco Trading Ltd.. The registry returned 2 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/dirtypornvids.com.
| Registered | since 7 Oct 2012 |
|---|---|
| Created | 7 October 2012 |
| Updated | 7 September 2026 |
| Expires | 7 October 2027 |
| Registrar | Danesco Trading Ltd. |
| Status | client delete prohibited, client transfer prohibited |
| Nameservers | ns1.dirtypornvids.com, ns2.dirtypornvids.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/dirtypornvids.com |
dirtypornvids.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.
dirtypornvids.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.dirtypornvids.com is published for dirtypornvids.com in the registration record from https://rdap.verisign.com/com/v1/domain/dirtypornvids.com.
Nameserver ns2.dirtypornvids.com is published for dirtypornvids.com in the registration record from https://rdap.verisign.com/com/v1/domain/dirtypornvids.com.
DNS
dirtypornvids.com has 2 address records, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 88.208.55.232 |
|---|---|
| AAAA | 2a02:b4a:1::5727:1 |
| NS | ns1.dirtypornvids.com, ns2.dirtypornvids.com |
| MX | dirtypornvids.com (10) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at dirtypornvids.com is "v=spf1 ip4:88.208.52.174/32 ~all".
The DMARC text record at _dmarc.dirtypornvids.com is "v=DMARC1; p=none; rua=mailto:[email protected]".
IPv4 address 88.208.55.232 answers for dirtypornvids.com at resolver 1.1.1.1:53.
IPv6 address 2a02:b4a:1::5727:1 answers for dirtypornvids.com at resolver 1.1.1.1:53.
Mail exchanger dirtypornvids.com has preference 10.
A random label under dirtypornvids.com also resolved, which means wildcard DNS is on.
Hosting and geo
dirtypornvids.com is placed in Amsterdam, The Netherlands by the local geolocation database (db-ip).
| Address | 88.208.55.232 |
|---|---|
| Country | The Netherlands |
| City | Amsterdam |
| Source | db-ip |
SSL/TLS
No TLS certificate was read for dirtypornvids.com on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
dial tcp 88.208.55.232:443: connect: connection refused
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://dirtypornvids.com/": dial tcp 88.208.55.232:443: connect: connection refused
Security
Family DNS for dirtypornvids.com is blocked, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | blocked |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Cloudflare family DNS returned a block for dirtypornvids.com. That resolver covers adult and malware names.
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 10 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 0 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 Amsterdam.
- October 2026: geo country changed from empty to The Netherlands.
Questions
Is dirtypornvids.com safe?
Cloudflare family DNS returned a block for dirtypornvids.com. That resolver covers adult and malware names.
Who hosts dirtypornvids.com?
dirtypornvids.com is placed in Amsterdam, The Netherlands.
When does dirtypornvids.com expire?
dirtypornvids.com expires on 7 October 2027 according to https://rdap.verisign.com/com/v1/domain/dirtypornvids.com.
Who owns dirtypornvids.com?
The registry did not return a person or a company for dirtypornvids.com. RDAP often redacts the registrant. The registrar on file is Danesco Trading Ltd..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/dirtypornvids.com at 2026-10-30T13:51:48Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:51:48Z
- TLS source tls:443 at 2026-10-30T13:51:48Z
- HTTP source https://dirtypornvids.com/ at 2026-10-30T13:51:48Z
- Tech source not available at 2026-10-30T13:51:48Z
- Geo source db-ip at 2026-10-30T13:51:48Z
- Safety source family DNS and local lists at 2026-10-30T13:51:48Z
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.