blockscode.com - robtex.com
blockscode.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 44.232.173.249🇺🇸 Amazon44.224.0.0/11 EC2 PDX prefix | ||||||
| PTR | ec2-44-232-173-249.us-west-2.compute.amazonaws.com | ||||||
| A | 52.40.42.113🇺🇸 Amazon52.40.0.0/14 EC2 PDX prefix | ||||||
| NS | launch1.spaceship.net ⭐ | ||||||
| A | 2400:cb00:2049:1::a29f:1a26🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.26.38Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | launch2.spaceship.net | ||||||
| A | 2400:cb00:2049:1::a29f:1b20🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.27.32Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| SOA | launch1.spaceship.netsupport@spaceship.com serial=1783363513 | ||||||
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1787159379 | ||||||
Same first word
blockscode.com |
Similar names
codeblocks.sk |
blockcodes.com |
decoblocks.com |
codeblocks.com |
codeblocks.de |
codeblocks.co |
codeblocks.org |
blockcodes.xyz |
codeblocks.pro |
codeblocks.bond |
Previous names
Next names
DNS History
22 records (4 active, 18 former)
○NSdns1.name-services.com2017-12-03 → 2017-12-03 · 4 obs
● 2017-12-03 00:53:06
○ 2026-08-19 16:24:08
○ 2026-08-19 17:36:32
○NSdns1.registrar-servers.com2016-12-19 → 2016-12-19 · 3 obs
○ 2017-12-03 00:53:06
○ 2026-08-19 17:36:32
○NSdns1.registrar-servers.com,2016-12-19 → 2016-12-19 · 3 obs
○ 2017-12-03 00:53:06
○ 2026-08-19 17:36:32
○NSdns2.name-services.com2017-12-03 → 2017-12-03 · 4 obs
● 2017-12-03 00:53:06
○ 2026-08-19 16:24:08
○ 2026-08-19 17:36:32
○NSdns2.registrar-servers.com2016-12-19 → 2016-12-19 · 3 obs
○ 2017-12-03 00:53:06
○ 2026-08-19 17:36:32
○NSdns3.name-services.com2017-12-03 → 2017-12-03 · 4 obs
● 2017-12-03 00:53:06
○ 2026-08-19 16:24:08
○ 2026-08-19 17:36:32
○NSdns3.registrar-servers.com2016-12-19 → 2016-12-19 · 3 obs
○ 2017-12-03 00:53:06
○ 2026-08-19 17:36:32
○NSdns4.name-services.com2017-12-03 → 2017-12-03 · 4 obs
● 2017-12-03 00:53:06
○ 2026-08-19 16:24:08
○ 2026-08-19 17:36:32
○NSdns4.registrar-servers.com2016-12-19 → 2016-12-19 · 3 obs
○ 2017-12-03 00:53:06
○ 2026-08-19 17:36:32
○NSdns5.name-services.com2017-12-03 → 2017-12-03 · 4 obs
● 2017-12-03 00:53:06
○ 2026-08-19 16:24:08
○ 2026-08-19 17:36:32
○NSdns5.registrar-servers.com2016-12-19 → 2016-12-19 · 3 obs
○ 2017-12-03 00:53:06
○ 2026-08-19 17:36:32
●NSlaunch1.spaceship.net2026-08-19 → 2026-08-19 · 3 obs
● 2026-08-19 16:24:08
● 2026-08-19 17:36:32
●NSlaunch2.spaceship.net2026-08-19 → 2026-08-19 · 3 obs
● 2026-08-19 16:24:08
● 2026-08-19 17:36:32
○MXeforward1.registrar-servers.com2016-12-19 → 2016-12-19 · 3 obs
○ 2017-12-03 00:53:06
○ 2026-08-19 17:36:32
○MXeforward2.registrar-servers.com2016-12-19 → 2016-12-19 · 3 obs
○ 2017-12-03 00:53:06
○ 2026-08-19 17:36:32
○MXeforward3.registrar-servers.com2016-12-19 → 2016-12-19 · 3 obs
○ 2017-12-03 00:53:06
○ 2026-08-19 17:36:32
○MXeforward4.registrar-servers.com2016-12-19 → 2016-12-19 · 3 obs
○ 2017-12-03 00:53:06
○ 2026-08-19 17:36:32
○MXeforward5.registrar-servers.com2016-12-19 → 2016-12-19 · 3 obs
○ 2017-12-03 00:53:06
○ 2026-08-19 17:36:32
○A192.64.119.112016-12-19 → 2016-12-19 · 3 obs
○ 2017-12-03 00:53:06
○ 2026-08-19 17:36:32
●A44.232.173.2492026-08-19 → 2026-08-19 · 3 obs
● 2026-08-19 16:24:08
● 2026-08-19 17:36:32
●A52.40.42.1132026-08-19 → 2026-08-19 · 3 obs
● 2026-08-19 16:24:08
● 2026-08-19 17:36:32
○A69.64.147.102017-12-03 → 2017-12-03 · 4 obs
● 2017-12-03 00:53:06
○ 2026-08-19 16:24:08
○ 2026-08-19 17:36:32
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | j.gtld-servers.net, m.gtld-servers.net, l.gtld-servers.net, i.gtld-servers.net... | - |
| blockscode.com | launch2.spaceship.net, launch1.spaceship.net | - |
✅ Authoritative Response
Server:162.159.27.32
NS records: launch2.spaceship.net, launch1.spaceship.net
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 362ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 52.40.42.113, 44.232.173.249 |
| NS | 2 | launch1.spaceship.net, launch2.spaceship.net |
| SOA | 1 | launch1.spaceship.net support.spaceship. |
Analysis
IP Addresses
blockscode.com has two IP addresses: 44.232.173.249 and 52.40.42.113
Additional host names — openaifactory.com, wcl.world, hemophagia.com and two others — share IP numbers with blockscode.com.
Name Servers
blockscode.com is delegated to two name servers: launch1.spaceship.net and launch2.spaceship.net.
blockscode.com shares its name server setup with other domains, including somose.com, chamadi.org, rely.de and two others.
blockscode.com has some name servers in common with other domains such as nationalastrology.com, soarmedicine.com and oasisrent.com
launch1.spaceship.net and launch2.spaceship.net each resolve to two IP addresses: launch1.spaceship.net points to 162.159.26.38 and 2400:cb00:2049:1::a29f:1a26, while launch2.spaceship.net points to 162.159.27.32 and 2400:cb00:2049:1::a29f:1b20.