insta-space.org
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeSSL: 463 days left8 years old
30
insta-space.org was registered on 10 Mar 2018 via Registrar of Domain Names REG.RU LLC and the registry expiry is 10 Mar 2027. WHOIS data came from RDAP at https://rdap.publicinterestregistry.org/rdap/domain/insta-space.org.
insta-space.org publishes 4 nameservers. DNSSEC is not signed.
insta-space.org has 1 IPv4 address (5.101.115.47). The geolocation database places 5.101.115.47 in Jõhvi, Estonia.
The TLS certificate from parking is not valid (TLS 1.2).
No safety warning was recorded for insta-space.org in the checks that ran.
Domain · RDAP/WHOIS
insta-space.org was registered on 10 Mar 2018 via Registrar of Domain Names REG.RU LLC. The registry returned 1 status value and 4 nameservers from https://rdap.publicinterestregistry.org/rdap/domain/insta-space.org.
| Registered | since 10 Mar 2018 |
|---|---|
| Created | 10 March 2018 |
| Updated | 11 August 2026 |
| Expires | 10 March 2027 |
| Registrar | Registrar of Domain Names REG.RU LLC |
| Status | client transfer prohibited |
| Nameservers | dns2.fastdns24.org, dns.fastdns24.com, dns3.fastdns24.eu, dns4.fastdns24.link |
| DNSSEC | no |
| Source | https://rdap.publicinterestregistry.org/rdap/domain/insta-space.org |
insta-space.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 dns2.fastdns24.org is published for insta-space.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/insta-space.org.
Nameserver dns.fastdns24.com is published for insta-space.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/insta-space.org.
Nameserver dns3.fastdns24.eu is published for insta-space.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/insta-space.org.
Nameserver dns4.fastdns24.link is published for insta-space.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/insta-space.org.
DNS
insta-space.org has 1 address record, 1 mail exchanger and 4 nameservers, measured at 1.1.1.1:53.
| A | 5.101.115.47 |
|---|---|
| AAAA | — |
| NS | dns.fastdns24.com, dns2.fastdns24.org, dns3.fastdns24.eu, dns4.fastdns24.link |
| MX | mx.yandex.net (10) |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 5.101.115.47 answers for insta-space.org at resolver 1.1.1.1:53.
Mail exchanger mx.yandex.net has preference 10.
Hosting and geo
insta-space.org is placed in Jõhvi, Estonia by the local geolocation database (db-ip).
| Address | 5.101.115.47 |
|---|---|
| Country | Estonia |
| City | Jõhvi |
| Source | db-ip |
SSL/TLS
The certificate for insta-space.org is not valid, with 463 days left and 0 subject alternative names. Source: tls:443.
| Issuer | parking |
|---|---|
| Subject | parking |
| Valid from | 8 February 2018 |
| Valid until | 6 February 2028 |
| Days left | 463 |
| SAN count | 0 |
| Protocol | TLS 1.2 |
| Source | tls:443 |
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://insta-space.org/": tls: failed to verify certificate: x509: certificate is not valid for any names, but wanted to match insta-space.org
Security
Family DNS for insta-space.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 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 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 Jõhvi.
- October 2026: geo country changed from empty to Estonia.
Questions
Is insta-space.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 insta-space.org?
insta-space.org is placed in Jõhvi, Estonia.
When does insta-space.org expire?
insta-space.org expires on 10 March 2027 according to https://rdap.publicinterestregistry.org/rdap/domain/insta-space.org.
Who owns insta-space.org?
The registry did not return a person or a company for insta-space.org. RDAP often redacts the registrant. The registrar on file is Registrar of Domain Names REG.RU LLC.
Sources
- RDAP source https://rdap.publicinterestregistry.org/rdap/domain/insta-space.org at 2026-10-30T15:02:40Z
- DNS source 1.1.1.1:53 at 2026-10-30T15:02:40Z
- TLS source tls:443 at 2026-10-30T15:02:40Z
- HTTP source https://insta-space.org/ at 2026-10-30T15:02:40Z
- Tech source not available at 2026-10-30T15:02:40Z
- Geo source db-ip at 2026-10-30T15:02:40Z
- Safety source family DNS and local lists at 2026-10-30T15:02:40Z
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.