jimperial.cc
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineFamily DNS blockedSSL: 26 days left1 year old
35
jimperial.cc was registered on 26 Oct 2025 via Treasure Trove Domains LLC and the registry expiry is 26 Oct 2027. WHOIS data came from RDAP at https://tld-rdap.verisign.com/cc/v1/domain/jimperial.cc.
jimperial.cc publishes 2 nameservers. DNSSEC is not signed.
jimperial.cc has 1 IPv4 address (77.247.179.87). The geolocation database places 77.247.179.87 in Amsterdam, The Netherlands.
The TLS certificate from YR1 is valid and has 26 days left (TLS 1.3).
Domain · RDAP/WHOIS
jimperial.cc was registered on 26 Oct 2025 via Treasure Trove Domains LLC. The registry returned 1 status value and 2 nameservers from https://tld-rdap.verisign.com/cc/v1/domain/jimperial.cc.
| Registered | since 26 Oct 2025 |
|---|---|
| Created | 26 October 2025 |
| Updated | 30 September 2026 |
| Expires | 26 October 2027 |
| Registrar | Treasure Trove Domains LLC |
| Status | active |
| Nameservers | ns1.badgerdns.com, ns2.badgerdns.com |
| DNSSEC | no |
| Source | https://tld-rdap.verisign.com/cc/v1/domain/jimperial.cc |
Nameserver ns1.badgerdns.com is published for jimperial.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/jimperial.cc.
Nameserver ns2.badgerdns.com is published for jimperial.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/jimperial.cc.
DNS
jimperial.cc has 1 address record, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 77.247.179.87 |
|---|---|
| AAAA | — |
| NS | ns1.badgerdns.com, ns2.badgerdns.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 77.247.179.87 answers for jimperial.cc at resolver 1.1.1.1:53.
A random label under jimperial.cc also resolved, which means wildcard DNS is on.
Hosting and geo
jimperial.cc is placed in Amsterdam, The Netherlands by the local geolocation database (db-ip).
| Address | 77.247.179.87 |
|---|---|
| Country | The Netherlands |
| City | Amsterdam |
| Source | db-ip |
SSL/TLS
The certificate for jimperial.cc is valid, with 26 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YR1 |
|---|---|
| Subject | jimperial.cc |
| Valid from | 28 August 2026 |
| Valid until | 26 November 2026 |
| Days left | 26 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.jimperial.cc, jimperial.cc.
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 |
|---|
Head "http://surveymrs.com": read tcp 10.0.0.3:42768->208.91.196.145:80: read: connection reset by peer
Security
Family DNS for jimperial.cc 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 jimperial.cc. 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 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: dns a changed from 77.247.179.90 to 77.247.179.87.
- October 2026: http status_class changed from 4xx to empty.
- October 2026: tech removed Cowboy.
- October 2026: tech removed Erlang.
- October 2026: geo city changed from empty to Amsterdam.
- October 2026: geo country changed from empty to The Netherlands.
Questions
Is jimperial.cc safe?
Cloudflare family DNS returned a block for jimperial.cc. That resolver covers adult and malware names.
Who hosts jimperial.cc?
jimperial.cc is placed in Amsterdam, The Netherlands.
When does jimperial.cc expire?
jimperial.cc expires on 26 October 2027 according to https://tld-rdap.verisign.com/cc/v1/domain/jimperial.cc.
Who owns jimperial.cc?
The registry did not return a person or a company for jimperial.cc. RDAP often redacts the registrant. The registrar on file is Treasure Trove Domains LLC.
Sources
- RDAP source https://tld-rdap.verisign.com/cc/v1/domain/jimperial.cc at 2026-10-30T13:34:18Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:34:18Z
- TLS source tls:443 at 2026-10-30T13:34:18Z
- HTTP source https://jimperial.cc/ at 2026-10-30T13:34:18Z
- Tech source not available at 2026-10-30T13:34:18Z
- Geo source db-ip at 2026-10-30T13:34:18Z
- Safety source family DNS and local lists at 2026-10-30T13:34:18Z
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.