dimeadozen.org
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafe21 years oldTranco #175925
40
dimeadozen.org was registered on 8 Apr 2005 via NameCheap, Inc. and the registry expiry is 8 Apr 2027. WHOIS data came from RDAP at https://rdap.publicinterestregistry.org/rdap/domain/dimeadozen.org.
dimeadozen.org publishes 2 nameservers. DNSSEC is not signed.
dimeadozen.org has 1 IPv4 address (66.36.229.22). The geolocation database places 66.36.229.22 in Washington D.C., United States.
No safety warning was recorded for dimeadozen.org in the checks that ran.
Domain · RDAP/WHOIS
dimeadozen.org was registered on 8 Apr 2005 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.publicinterestregistry.org/rdap/domain/dimeadozen.org.
| Registered | since 8 Apr 2005 |
|---|---|
| Created | 8 April 2005 |
| Updated | 12 August 2026 |
| Expires | 8 April 2027 |
| Registrar | NameCheap, Inc. |
| Status | client transfer prohibited |
| Nameservers | ns1.dimeadozen.org, ns2.dimeadozen.org |
| DNSSEC | no |
| Source | https://rdap.publicinterestregistry.org/rdap/domain/dimeadozen.org |
dimeadozen.org 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.dimeadozen.org is published for dimeadozen.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/dimeadozen.org.
Nameserver ns2.dimeadozen.org is published for dimeadozen.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/dimeadozen.org.
DNS
dimeadozen.org has 1 address record, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 66.36.229.22 |
|---|---|
| AAAA | — |
| NS | ns1.dimeadozen.org, ns2.dimeadozen.org |
| MX | mx1.dimeadozen.org (10) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at dimeadozen.org is "v=spf1 a mx ip4:85.25.194.36/32 ip4:66.36.229.22/32 ip4:66.36.229.23/32 ip4:62.138.14.107 -all".
The DMARC text record at _dmarc.dimeadozen.org is "v=DMARC1; p=reject; rua=mailto:[email protected]; pct=100; ruf=mailto:[email protected]; fo=0:d:s; aspf=r; adkim=r;".
IPv4 address 66.36.229.22 answers for dimeadozen.org at resolver 1.1.1.1:53.
Mail exchanger mx1.dimeadozen.org has preference 10.
Hosting and geo
dimeadozen.org is placed in Washington D.C., United States by the local geolocation database (db-ip).
| Address | 66.36.229.22 |
|---|---|
| Country | United States |
| City | Washington D.C. |
| Source | db-ip |
SSL/TLS
No TLS certificate was read for dimeadozen.org on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
dial tcp 66.36.229.22: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://dimeadozen.org/": dial tcp 66.36.229.22:443: connect: connection refused
Security
Family DNS for dimeadozen.org 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 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 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 Washington D.C..
- October 2026: geo country changed from empty to United States.
Questions
Is dimeadozen.org 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 dimeadozen.org?
dimeadozen.org is placed in Washington D.C., United States.
When does dimeadozen.org expire?
dimeadozen.org expires on 8 April 2027 according to https://rdap.publicinterestregistry.org/rdap/domain/dimeadozen.org.
Who owns dimeadozen.org?
The registry did not return a person or a company for dimeadozen.org. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..
Sources
- RDAP source https://rdap.publicinterestregistry.org/rdap/domain/dimeadozen.org at 2026-10-30T15:01:54Z
- DNS source 1.1.1.1:53 at 2026-10-30T15:01:54Z
- TLS source tls:443 at 2026-10-30T15:01:54Z
- HTTP source https://dimeadozen.org/ at 2026-10-30T15:01:54Z
- Tech source not available at 2026-10-30T15:01:54Z
- Geo source db-ip at 2026-10-30T15:01:54Z
- Safety source family DNS and local lists at 2026-10-30T15:01:54Z
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.