simp3.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineFamily DNS blockedSSL: 161 days left10 years old
15
simp3.com was registered on 2 Dec 2015 via Name.com, Inc. and the registry expiry is 2 Dec 2026. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/simp3.com.
simp3.com has 1 IPv4 address (52.223.39.56). The geolocation database places 52.223.39.56 in Montreal, Canada.
The TLS certificate from Amazon RSA 2048 M04 is not valid (TLS 1.3).
Domain · RDAP/WHOIS
simp3.com was registered on 2 Dec 2015 via Name.com, Inc.. The registry returned 4 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/simp3.com.
| Registered | since 2 Dec 2015 |
|---|---|
| Created | 2 December 2015 |
| Updated | 3 December 2025 |
| Expires | 2 December 2026 |
| Registrar | Name.com, Inc. |
| Status | client transfer prohibited, server delete prohibited, server transfer prohibited, server update prohibited |
| Nameservers | ns1.seizedservers.com, ns2.seizedservers.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/simp3.com |
simp3.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.
simp3.com carries the status "server delete prohibited". The registry itself is refusing deletes. This lock is not one the registrar can clear alone.
simp3.com carries the status "server transfer prohibited". The registry itself is refusing transfers. The name stays at the current registrar while the status remains.
simp3.com carries the status "server update prohibited". The registry itself is refusing updates to the domain object.
Nameserver ns1.seizedservers.com is published for simp3.com in the registration record from https://rdap.verisign.com/com/v1/domain/simp3.com.
Nameserver ns2.seizedservers.com is published for simp3.com in the registration record from https://rdap.verisign.com/com/v1/domain/simp3.com.
DNS
simp3.com has 1 address record, 0 mail exchangers and 0 nameservers, measured at 1.1.1.1:53.
| A | 52.223.39.56 |
|---|---|
| AAAA | — |
| NS | — |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 52.223.39.56 answers for simp3.com at resolver 1.1.1.1:53.
A random label under simp3.com also resolved, which means wildcard DNS is on.
Hosting and geo
simp3.com is placed in Montreal, Canada by the local geolocation database (db-ip).
| Address | 52.223.39.56 |
|---|---|
| Country | Canada |
| City | Montreal |
| Source | db-ip |
SSL/TLS
The certificate for simp3.com is not valid, with 161 days left and 2 subject alternative names. Source: tls:443.
| Issuer | Amazon RSA 2048 M04 |
|---|---|
| Subject | seizedservers.com |
| Valid from | 25 September 2026 |
| Valid until | 10 April 2027 |
| Days left | 161 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.seizedservers.com, seizedservers.com.
Validation result: certificate did not validate
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://simp3.com/": tls: failed to verify certificate: x509: certificate is valid for seizedservers.com, *.seizedservers.com, not simp3.com
Security
Family DNS for simp3.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 simp3.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 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: geo city changed from empty to Montreal.
- October 2026: geo country changed from empty to Canada.
Questions
Is simp3.com safe?
Cloudflare family DNS returned a block for simp3.com. That resolver covers adult and malware names.
Who hosts simp3.com?
simp3.com is placed in Montreal, Canada.
When does simp3.com expire?
simp3.com expires on 2 December 2026 according to https://rdap.verisign.com/com/v1/domain/simp3.com.
Who owns simp3.com?
The registry did not return a person or a company for simp3.com. RDAP often redacts the registrant. The registrar on file is Name.com, Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/simp3.com at 2026-10-30T14:14:05Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:14:05Z
- TLS source tls:443 at 2026-10-30T14:14:05Z
- HTTP source https://simp3.com/ at 2026-10-30T14:14:05Z
- Tech source not available at 2026-10-30T14:14:05Z
- Geo source db-ip at 2026-10-30T14:14:05Z
- Safety source family DNS and local lists at 2026-10-30T14:14:05Z
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.