codingagent.com - robtex.com
codingagent.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=1785801958 | ||||||
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=1786720314 | ||||||
Previously MX for
codingagent.com |
Same first word
codingagent.com |
DNS History
11 records (4 active, 7 former)
βNSlaunch1.spaceship.net2026-03-24 β 2026-08-14 Β· 3 obs
β 2026-03-24 15:47:16
β 2026-08-14 15:35:50
βNSlaunch2.spaceship.net2026-03-24 β 2026-08-14 Β· 3 obs
β 2026-03-24 15:47:16
β 2026-08-14 15:35:50
βNSns1.diehardhost.com2015-07-10 β 2017-01-05 Β· 4 obs
β 2017-01-05 15:04:16
β 2019-03-13 16:25:32
β 2026-08-14 15:35:50
βNSns1.dynadot.com2019-03-13 β 2019-03-13 Β· 4 obs
β 2019-03-13 16:25:32
β 2026-03-24 15:47:16
β 2026-08-14 15:35:50
βNSns2.diehardhost.com2015-07-10 β 2017-01-05 Β· 4 obs
β 2017-01-05 15:04:16
β 2019-03-13 16:25:32
β 2026-08-14 15:35:50
βNSns2.dynadot.com2019-03-13 β 2019-03-13 Β· 4 obs
β 2019-03-13 16:25:32
β 2026-03-24 15:47:16
β 2026-08-14 15:35:50
βMXcodingagent.com2015-07-10 β 2017-01-05 Β· 4 obs
β 2017-01-05 15:04:16
β 2019-03-13 16:25:32
β 2026-08-14 15:35:50
βA207.126.160.1322015-07-10 β 2017-01-05 Β· 4 obs
β 2017-01-05 15:04:16
β 2019-03-13 16:25:32
β 2026-08-14 15:35:50
βA44.232.173.2492026-03-24 β 2026-08-14 Β· 3 obs
β 2026-03-24 15:47:16
β 2026-08-14 15:35:50
βA52.0.217.442019-03-13 β 2019-03-13 Β· 4 obs
β 2019-03-13 16:25:32
β 2026-03-24 15:47:16
β 2026-08-14 15:35:50
βA52.40.42.1132026-03-24 β 2026-08-14 Β· 3 obs
β 2026-03-24 15:47:16
β 2026-08-14 15:35:50
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| codingagent.com | launch2.spaceship.net, launch1.spaceship.net | - |
β Authoritative Response
Server:162.159.27.32
NS records: launch2.spaceship.net, launch1.spaceship.net
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for codingagent.com (unsigned zone)
β±οΈ Timing
Total: 349ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 52.40.42.113, 44.232.173.249 |
| NS | 2 | launch2.spaceship.net, launch1.spaceship.net |
| SOA | 1 | launch1.spaceship.net support.spaceship. |
Analysis
IP Addresses
codingagent.com has two IP addresses: 44.232.173.249 and 52.40.42.113
Two other host names, along with promosyon.org, lkug.com and (0x736578)iestalpha.com, also share IP numbers with codingagent.com.
Name Servers
codingagent.com is delegated to two name servers: launch1.spaceship.net and launch2.spaceship.net.
codingagent.com shares its NS records with other domains, for example wipr.xyz, x402.casino, 100252.com and two others.
The name servers of codingagent.com overlap at least partially with those of other domains β among them deckortimber.co.uk, milleniadayspa.com, operaize.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.