codingfly.com - dns.ninja
codingfly.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 | 9ce24594-a783-4a70-b38d-524abd2bb34e | ||||||
| SOA | launch1.spaceship.netsupport@spaceship.com serial=1779029167 | ||||||
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=1782500435 | ||||||
Subdomains
www.codingfly.com |
Same first word
codingfly.de |
codingfly.com |
Similar names
DNS History
10 records (4 active, 6 former)
○NSdns13.hichina.com2015-07-03 → 2016-05-04 · 4 obs
● 2016-05-04 06:09:08
○ 2017-02-17 11:07:44
○ 2026-06-26 19:23:28
○NSdns14.hichina.com2015-07-03 → 2016-05-04 · 4 obs
● 2016-05-04 06:09:08
○ 2017-02-17 11:07:44
○ 2026-06-26 19:23:28
●NSlaunch1.spaceship.net2026-02-18 → 2026-06-26 · 3 obs
● 2026-02-18 04:46:56
● 2026-06-26 19:23:28
●NSlaunch2.spaceship.net2026-02-18 → 2026-06-26 · 3 obs
● 2026-02-18 04:46:56
● 2026-06-26 19:23:28
○NSns1.bdydns.cn2019-04-02 → 2019-04-02 · 4 obs
● 2019-04-02 13:33:06
○ 2026-02-18 04:46:56
○ 2026-06-26 19:23:28
○NSns2.bdydns.cn2019-04-02 → 2019-04-02 · 4 obs
● 2019-04-02 13:33:06
○ 2026-02-18 04:46:56
○ 2026-06-26 19:23:28
○MXmx.ym.163.com2019-04-02 → 2019-04-02 · 3 obs
○ 2026-02-18 04:46:56
○ 2026-06-26 19:23:28
○A180.76.238.932019-04-02 → 2019-04-02 · 3 obs
○ 2026-02-18 04:46:56
○ 2026-06-26 19:23:28
●A44.232.173.2492026-02-18 → 2026-06-26 · 3 obs
● 2026-02-18 04:46:56
● 2026-06-26 19:23:28
●A52.40.42.1132026-02-18 → 2026-06-26 · 3 obs
● 2026-02-18 04:46:56
● 2026-06-26 19:23:28
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | k.gtld-servers.net, a.gtld-servers.net, m.gtld-servers.net, e.gtld-servers.net... | - |
| codingfly.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 codingfly.com (unsigned zone)
⏱️ Timing
Total: 1056ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 52.40.42.113, 44.232.173.249 |
| NS | 2 | launch2.spaceship.net, launch1.spaceship.net |
| TXT | 1 | 9ce24594-a783-4a70-b38d-524abd2bb34e |
| SOA | 1 | launch1.spaceship.net support.spaceship. |
Analysis
Hierarchy
codingfly.com is the parent zone for www.codingfly.com.
IP Addresses
codingfly.com resolves to the IP addresses 44.232.173.249 and 52.40.42.113
Additional host names — portafino.com, yangtse.net, 3c.ai and two others — share IP numbers with codingfly.com.
Name Servers
codingfly.com has two authoritative name servers — launch1.spaceship.net and launch2.spaceship.net.
codingfly.com shares its name server setup with other domains, including vic.vc, fafa212vip.com, predictroyal.com and two others.
codingfly.com partially shares its name servers with domains like mibrillante.com and whatagym.com.
Both launch1.spaceship.net and launch2.spaceship.net have two IP addresses each. launch1.spaceship.net resolves to 162.159.26.38 and 2400:cb00:2049:1::a29f:1a26; launch2.spaceship.net resolves to 162.159.27.32 and 2400:cb00:2049:1::a29f:1b20.