dirtyship.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
HTTP 403Family DNS blockedSSL: 57 days left8 years oldTranco #61494
40
dirtyship.com was registered on 12 Oct 2018 via eNom, LLC and the registry expiry is 12 Oct 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/dirtyship.com.
dirtyship.com publishes 2 nameservers. DNSSEC is not signed.
dirtyship.com has 2 IPv4 addresses (188.114.96.3, 188.114.97.3) and 2 IPv6 addresses (2a06:98c1:3120::4, 2a06:98c1:3121::4). The geolocation database places 188.114.96.3 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 57 days left (TLS 1.2).
Tech detection named Cloudflare. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
dirtyship.com was registered on 12 Oct 2018 via eNom, LLC. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/dirtyship.com.
| Registered | since 12 Oct 2018 |
|---|---|
| Created | 12 October 2018 |
| Updated | 26 September 2025 |
| Expires | 12 October 2027 |
| Registrar | eNom, LLC |
| Status | client transfer prohibited |
| Nameservers | jade.ns.cloudflare.com, wesley.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/dirtyship.com |
dirtyship.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 jade.ns.cloudflare.com is published for dirtyship.com in the registration record from https://rdap.verisign.com/com/v1/domain/dirtyship.com.
Nameserver wesley.ns.cloudflare.com is published for dirtyship.com in the registration record from https://rdap.verisign.com/com/v1/domain/dirtyship.com.
DNS
dirtyship.com has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 188.114.96.3, 188.114.97.3 |
|---|---|
| AAAA | 2a06:98c1:3120::4, 2a06:98c1:3121::4 |
| NS | jade.ns.cloudflare.com, wesley.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 188.114.96.3 answers for dirtyship.com at resolver 1.1.1.1:53.
IPv4 address 188.114.97.3 answers for dirtyship.com at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3120::4 answers for dirtyship.com at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3121::4 answers for dirtyship.com at resolver 1.1.1.1:53.
Hosting and geo
dirtyship.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 188.114.96.3 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for dirtyship.com is valid, with 57 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | dirtyship.com |
| Valid from | 29 September 2026 |
| Valid until | 28 December 2026 |
| Days left | 57 |
| SAN count | 2 |
| Protocol | TLS 1.2 |
| Source | tls:443 |
Subject alternative names: *.dirtyship.com, dirtyship.com.
Tech stack
Tech detection checked the fetched homepage and named 1 product. Source: wappalyzergo.
- Cloudflare · CDN
Cloudflare is filed under CDN.
On-page checks
The homepage returned HTTP 403 in 20 ms. The target title is 93 characters and the page has 1 H1 heading.
| Status | 403 |
|---|---|
| TTFB | 20 ms |
| Title length | 93 no |
| Quoted title | "Access denied | dirtyship.com used Cloudflare to restrict access | dirtyship.com | Cloudflare" |
| Meta description | none no |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | noindex, nofollow |
| Canonical | — |
| Language | en-US |
| Links | 2 |
| 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 dirtyship.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 dirtyship.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 20 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 5 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: dns a changed from 188.114.96.4,188.114.97.4 to 188.114.96.3,188.114.97.3.
- October 2026: dns aaaa changed from 2a06:98c1:3120::3,2a06:98c1:3121::3 to 2a06:98c1:3120::4,2a06:98c1:3121::4.
Questions
Is dirtyship.com safe?
Cloudflare family DNS returned a block for dirtyship.com. That resolver covers adult and malware names.
Who hosts dirtyship.com?
dirtyship.com is placed in Toronto, Canada.
When does dirtyship.com expire?
dirtyship.com expires on 12 October 2027 according to https://rdap.verisign.com/com/v1/domain/dirtyship.com.
Who owns dirtyship.com?
The registry did not return a person or a company for dirtyship.com. RDAP often redacts the registrant. The registrar on file is eNom, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/dirtyship.com at 2026-10-30T13:51:47Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:51:47Z
- TLS source tls:443 at 2026-10-30T13:51:47Z
- HTTP source https://dirtyship.com/ at 2026-10-30T13:51:47Z
- Tech source wappalyzergo at 2026-10-30T13:51:47Z
- Geo source db-ip at 2026-10-30T13:51:47Z
- Safety source family DNS and local lists at 2026-10-30T13:51:47Z
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.