codesolutions.com - dns.ninja
codesolutions.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 | ||||||
| TXT | 07cad280-3d76-4377-9813-be0852ffe6e4 | ||||||
| SOA | launch1.spaceship.netsupport@spaceship.com serial=1779783366 | ||||||
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=1783254616 | ||||||
Same first word
codesolutions.net |
codesolutions.com |
codesolutions.eu |
codesolutions.de |
codesolutions.io |
codesolutions.pro |
codesolutions.fi |
codesolutions.ca |
codesolutions.co |
Similar names
sedcosolution.com |
edocsolutions.com |
decosolutions.ca |
consolestudio.click |
studioconsole.com |
solutionscode.com |
edocsolutions.de |
DNS History
21 records (4 active, 17 former)
○NSbuy.internettraffic.com2015-08-05 → 2016-08-14 · 5 obs
○ 2009-01-09 22:47:54
● 2015-08-05 03:59:06
● 2016-08-14 04:57:20
○ 2017-04-04 09:35:36
○ 2026-07-05 13:17:40
● 2015-08-05 03:59:06
● 2016-08-14 04:57:20
○ 2017-04-04 09:35:36
○ 2026-07-05 13:17:40
●NSlaunch1.spaceship.net2026-07-05 → 2026-07-05 · 3 obs
○ 2026-03-09 17:55:46
● 2026-07-05 13:17:38
● 2026-07-05 13:17:40
● 2026-07-05 13:17:38
● 2026-07-05 13:17:40
●NSlaunch2.spaceship.net2026-07-05 → 2026-07-05 · 3 obs
○ 2026-03-09 17:55:46
● 2026-07-05 13:17:38
● 2026-07-05 13:17:40
● 2026-07-05 13:17:38
● 2026-07-05 13:17:40
○NSns.real-time.com2009-01-09 → 2009-01-09 · 3 obs
● 2009-01-09 22:47:54
○ 2015-08-05 03:59:06
○ 2026-07-05 13:17:40
○ 2015-08-05 03:59:06
○ 2026-07-05 13:17:40
○NSns1.parkingcrew.net2026-03-09 → 2026-03-09 · 4 obs
○ 2020-03-09 11:42:12
● 2026-03-09 17:55:46
○ 2026-07-05 13:17:38
○ 2026-07-05 13:17:40
● 2026-03-09 17:55:46
○ 2026-07-05 13:17:38
○ 2026-07-05 13:17:40
○NSns1.real-time.com2009-01-09 → 2009-01-09 · 3 obs
● 2009-01-09 22:47:54
○ 2015-08-05 03:59:06
○ 2026-07-05 13:17:40
○ 2015-08-05 03:59:06
○ 2026-07-05 13:17:40
○NSns1.uniregistrymarket.link2017-04-04 → 2020-03-09 · 5 obs
○ 2016-08-14 04:57:20
● 2017-04-04 09:35:36
● 2020-03-09 11:42:12
○ 2026-03-09 17:55:46
○ 2026-07-05 13:17:40
● 2017-04-04 09:35:36
● 2020-03-09 11:42:12
○ 2026-03-09 17:55:46
○ 2026-07-05 13:17:40
○NSns2.parkingcrew.net2026-03-09 → 2026-03-09 · 4 obs
○ 2020-03-09 11:42:12
● 2026-03-09 17:55:46
○ 2026-07-05 13:17:38
○ 2026-07-05 13:17:40
● 2026-03-09 17:55:46
○ 2026-07-05 13:17:38
○ 2026-07-05 13:17:40
○NSns2.real-time.com2009-01-09 → 2009-01-09 · 3 obs
● 2009-01-09 22:47:54
○ 2015-08-05 03:59:06
○ 2026-07-05 13:17:40
○ 2015-08-05 03:59:06
○ 2026-07-05 13:17:40
○NSns2.uniregistrymarket.link2017-04-04 → 2020-03-09 · 5 obs
○ 2016-08-14 04:57:20
● 2017-04-04 09:35:36
● 2020-03-09 11:42:12
○ 2026-03-09 17:55:46
○ 2026-07-05 13:17:40
● 2017-04-04 09:35:36
● 2020-03-09 11:42:12
○ 2026-03-09 17:55:46
○ 2026-07-05 13:17:40
○NSsell.internettraffic.com2015-08-05 → 2016-08-14 · 5 obs
○ 2009-01-09 22:47:54
● 2015-08-05 03:59:06
● 2016-08-14 04:57:20
○ 2017-04-04 09:35:36
○ 2026-07-05 13:17:40
● 2015-08-05 03:59:06
● 2016-08-14 04:57:20
○ 2017-04-04 09:35:36
○ 2026-07-05 13:17:40
○MXmail.h-email.net2026-03-09 → 2026-03-09 · 4 obs
○ 2020-03-09 11:42:12
● 2026-03-09 17:55:46
○ 2026-07-05 13:17:38
○ 2026-07-05 13:17:40
● 2026-03-09 17:55:46
○ 2026-07-05 13:17:38
○ 2026-07-05 13:17:40
○MXmx247.in-mx.com2020-03-09 → 2020-03-09 · 4 obs
○ 2015-08-05 03:59:06
● 2020-03-09 11:42:12
○ 2026-03-09 17:55:46
○ 2026-07-05 13:17:40
● 2020-03-09 11:42:12
○ 2026-03-09 17:55:46
○ 2026-07-05 13:17:40
○MXmx247.in-mx.net2020-03-09 → 2020-03-09 · 4 obs
○ 2015-08-05 03:59:06
● 2020-03-09 11:42:12
○ 2026-03-09 17:55:46
○ 2026-07-05 13:17:40
● 2020-03-09 11:42:12
○ 2026-03-09 17:55:46
○ 2026-07-05 13:17:40
○MXsmtpgrey-1.real-time.com2009-01-09 → 2009-01-09 · 3 obs
● 2009-01-09 22:47:54
○ 2015-08-05 03:59:06
○ 2026-07-05 13:17:40
○ 2015-08-05 03:59:06
○ 2026-07-05 13:17:40
○MXsmtpgrey-2.real-time.com2009-01-09 → 2009-01-09 · 3 obs
● 2009-01-09 22:47:54
○ 2015-08-05 03:59:06
○ 2026-07-05 13:17:40
○ 2015-08-05 03:59:06
○ 2026-07-05 13:17:40
○A104.247.81.992026-03-09 → 2026-03-09 · 4 obs
○ 2020-03-09 11:42:12
● 2026-03-09 17:55:46
○ 2026-07-05 13:17:38
○ 2026-07-05 13:17:40
● 2026-03-09 17:55:46
○ 2026-07-05 13:17:38
○ 2026-07-05 13:17:40
●A44.232.173.2492026-07-05 → 2026-07-05 · 3 obs
○ 2026-03-09 17:55:46
● 2026-07-05 13:17:38
● 2026-07-05 13:17:40
● 2026-07-05 13:17:38
● 2026-07-05 13:17:40
●A52.40.42.1132026-07-05 → 2026-07-05 · 3 obs
○ 2026-03-09 17:55:46
● 2026-07-05 13:17:38
● 2026-07-05 13:17:40
● 2026-07-05 13:17:38
● 2026-07-05 13:17:40
○A69.172.201.1532016-08-14 → 2020-03-09 · 5 obs
○ 2016-03-18 22:13:56
● 2016-08-14 04:57:20
● 2020-03-09 11:42:12
○ 2026-03-09 17:55:46
○ 2026-07-05 13:17:40
● 2016-08-14 04:57:20
● 2020-03-09 11:42:12
○ 2026-03-09 17:55:46
○ 2026-07-05 13:17:40
○A69.172.201.2082015-08-05 → 2016-03-18 · 5 obs
○ 2009-01-09 22:47:54
● 2015-08-05 03:59:06
● 2016-03-18 22:13:56
○ 2016-08-14 04:57:20
○ 2026-07-05 13:17:40
● 2015-08-05 03:59:06
● 2016-03-18 22:13:56
○ 2016-08-14 04:57:20
○ 2026-07-05 13:17:40
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| codesolutions.com | launch2.spaceship.net, launch1.spaceship.net | - |
✅ Authoritative Response
Server:162.159.26.38
NS records: launch2.spaceship.net, launch1.spaceship.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for codesolutions.com (unsigned zone)
⏱️ Timing
Total: 1605ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 44.232.173.249, 52.40.42.113 |
| NS | 2 | launch2.spaceship.net, launch1.spaceship.net |
| TXT | 1 | 07cad280-3d76-4377-9813-be0852ffe6e4 |
| SOA | 1 | launch1.spaceship.net support.spaceship. |
Analysis
IP Addresses
codesolutions.com resolves to the IP addresses 44.232.173.249 and 52.40.42.113
Among the host names that share IP numbers with codesolutions.com are natations.com, alquilerdevacaciones.com, gasoft.com and two others.
Name Servers
codesolutions.com is delegated to two name servers: launch1.spaceship.net and launch2.spaceship.net.
codesolutions.com has the same name server delegation as a number of other domains, such as racunaj.me, ppbseq.com, pevn.com and two more.
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.