sinoengineers.com - robtex.com
sinoengineers.com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| A | 54.148.98.255🇺🇸 Amazon54.148.0.0/15 EC2 PDX prefix | ||||||
| PTR | ec2-54-148-98-255.us-west-2.compute.amazonaws.com | ||||||
| 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=1762739051 | ||||||
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=1774520582 | ||||||
Same first word
sinoengineers.com |
DNS History
23 records (3 active, 20 former)
●NSlaunch1.spaceship.net2026-02-25 → 2026-03-26 · 3 obs
○ 2017-10-09 20:45:02
● 2026-02-25 01:30:58
● 2026-03-26 10:41:12
● 2026-02-25 01:30:58
● 2026-03-26 10:41:12
●NSlaunch2.spaceship.net2026-02-25 → 2026-03-26 · 3 obs
○ 2017-10-09 20:45:02
● 2026-02-25 01:30:58
● 2026-03-26 10:41:12
● 2026-02-25 01:30:58
● 2026-03-26 10:41:12
○NSns1.dnsowl.com2016-04-03 → 2017-10-09 · 5 obs
○ 2016-01-12 04:47:44
● 2016-04-03 01:50:02
● 2017-10-09 20:45:02
○ 2026-02-25 01:30:58
○ 2026-03-26 10:41:12
● 2016-04-03 01:50:02
● 2017-10-09 20:45:02
○ 2026-02-25 01:30:58
○ 2026-03-26 10:41:12
○NSns1cnb.domain-resolution.net2015-07-17 → 2016-01-12 · 5 obs
○ 2007-11-11 00:20:36
● 2015-07-17 05:27:06
● 2016-01-12 04:47:44
○ 2016-04-03 01:50:02
○ 2026-03-26 10:41:12
● 2015-07-17 05:27:06
● 2016-01-12 04:47:44
○ 2016-04-03 01:50:02
○ 2026-03-26 10:41:12
○NSns2.dnsowl.com2016-04-03 → 2017-10-09 · 5 obs
○ 2016-01-12 04:47:44
● 2016-04-03 01:50:02
● 2017-10-09 20:45:02
○ 2026-02-25 01:30:58
○ 2026-03-26 10:41:12
● 2016-04-03 01:50:02
● 2017-10-09 20:45:02
○ 2026-02-25 01:30:58
○ 2026-03-26 10:41:12
○NSns2fkr.domain-resolution.net2015-07-17 → 2016-01-12 · 5 obs
○ 2007-11-11 00:20:36
● 2015-07-17 05:27:06
● 2016-01-12 04:47:44
○ 2016-04-03 01:50:02
○ 2026-03-26 10:41:12
● 2015-07-17 05:27:06
● 2016-01-12 04:47:44
○ 2016-04-03 01:50:02
○ 2026-03-26 10:41:12
○NSns3.dnsowl.com2016-04-03 → 2017-10-09 · 5 obs
○ 2016-01-12 04:47:44
● 2016-04-03 01:50:02
● 2017-10-09 20:45:02
○ 2026-02-25 01:30:58
○ 2026-03-26 10:41:12
● 2016-04-03 01:50:02
● 2017-10-09 20:45:02
○ 2026-02-25 01:30:58
○ 2026-03-26 10:41:12
○NSns31.domaincontrol.com2007-11-11 → 2007-11-11 · 3 obs
● 2007-11-11 00:20:36
○ 2015-07-17 05:27:06
○ 2026-03-26 10:41:12
○ 2015-07-17 05:27:06
○ 2026-03-26 10:41:12
○NSns32.domaincontrol.com2007-11-11 → 2007-11-11 · 3 obs
● 2007-11-11 00:20:36
○ 2015-07-17 05:27:06
○ 2026-03-26 10:41:12
○ 2015-07-17 05:27:06
○ 2026-03-26 10:41:12
○NSns3cna.domain-resolution.net2015-07-17 → 2016-01-12 · 5 obs
○ 2007-11-11 00:20:36
● 2015-07-17 05:27:06
● 2016-01-12 04:47:44
○ 2016-04-03 01:50:02
○ 2026-03-26 10:41:12
● 2015-07-17 05:27:06
● 2016-01-12 04:47:44
○ 2016-04-03 01:50:02
○ 2026-03-26 10:41:12
○NSns4fpy.domain-resolution.net2015-07-17 → 2016-01-12 · 5 obs
○ 2007-11-11 00:20:36
● 2015-07-17 05:27:06
● 2016-01-12 04:47:44
○ 2016-04-03 01:50:02
○ 2026-03-26 10:41:12
● 2015-07-17 05:27:06
● 2016-01-12 04:47:44
○ 2016-04-03 01:50:02
○ 2026-03-26 10:41:12
○MXmailstore1.secureserver.net2007-11-11 → 2007-11-11 · 3 obs
● 2007-11-11 00:20:36
○ 2015-07-17 05:27:06
○ 2026-03-26 10:41:12
○ 2015-07-17 05:27:06
○ 2026-03-26 10:41:12
○MXmx3.name.com2015-07-17 → 2017-10-09 · 5 obs
○ 2007-11-11 00:20:36
● 2015-07-17 05:27:06
● 2017-10-09 20:45:02
○ 2026-02-25 01:30:58
○ 2026-03-26 10:41:12
● 2015-07-17 05:27:06
● 2017-10-09 20:45:02
○ 2026-02-25 01:30:58
○ 2026-03-26 10:41:12
○MXmx4.name.com2015-07-17 → 2017-10-09 · 5 obs
○ 2007-11-11 00:20:36
● 2015-07-17 05:27:06
● 2017-10-09 20:45:02
○ 2026-02-25 01:30:58
○ 2026-03-26 10:41:12
● 2015-07-17 05:27:06
● 2017-10-09 20:45:02
○ 2026-02-25 01:30:58
○ 2026-03-26 10:41:12
○MXmx5.name.com2015-07-17 → 2017-10-09 · 5 obs
○ 2007-11-11 00:20:36
● 2015-07-17 05:27:06
● 2017-10-09 20:45:02
○ 2026-02-25 01:30:58
○ 2026-03-26 10:41:12
● 2015-07-17 05:27:06
● 2017-10-09 20:45:02
○ 2026-02-25 01:30:58
○ 2026-03-26 10:41:12
○MXmx6.name.com2015-07-17 → 2017-10-09 · 5 obs
○ 2007-11-11 00:20:36
● 2015-07-17 05:27:06
● 2017-10-09 20:45:02
○ 2026-02-25 01:30:58
○ 2026-03-26 10:41:12
● 2015-07-17 05:27:06
● 2017-10-09 20:45:02
○ 2026-02-25 01:30:58
○ 2026-03-26 10:41:12
○MXmx7.name.com2015-07-17 → 2017-10-09 · 5 obs
○ 2007-11-11 00:20:36
● 2015-07-17 05:27:06
● 2017-10-09 20:45:02
○ 2026-02-25 01:30:58
○ 2026-03-26 10:41:12
● 2015-07-17 05:27:06
● 2017-10-09 20:45:02
○ 2026-02-25 01:30:58
○ 2026-03-26 10:41:12
○MXmx8.name.com2015-07-17 → 2017-10-09 · 5 obs
○ 2007-11-11 00:20:36
● 2015-07-17 05:27:06
● 2017-10-09 20:45:02
○ 2026-02-25 01:30:58
○ 2026-03-26 10:41:12
● 2015-07-17 05:27:06
● 2017-10-09 20:45:02
○ 2026-02-25 01:30:58
○ 2026-03-26 10:41:12
○MXsmtp.secureserver.net2007-11-11 → 2007-11-11 · 3 obs
● 2007-11-11 00:20:36
○ 2015-07-17 05:27:06
○ 2026-03-26 10:41:12
○ 2015-07-17 05:27:06
○ 2026-03-26 10:41:12
●A54.148.98.2552026-02-25 → 2026-03-26 · 3 obs
○ 2017-10-09 20:45:02
● 2026-02-25 01:30:58
● 2026-03-26 10:41:12
● 2026-02-25 01:30:58
● 2026-03-26 10:41:12
○A54.209.29.2102016-04-03 → 2017-10-09 · 5 obs
○ 2016-01-12 04:47:44
● 2016-04-03 01:50:02
● 2017-10-09 20:45:02
○ 2026-02-25 01:30:58
○ 2026-03-26 10:41:12
● 2016-04-03 01:50:02
● 2017-10-09 20:45:02
○ 2026-02-25 01:30:58
○ 2026-03-26 10:41:12
○A68.178.232.1002007-11-11 → 2007-11-11 · 3 obs
● 2007-11-11 00:20:36
○ 2015-07-17 05:27:06
○ 2026-03-26 10:41:12
○ 2015-07-17 05:27:06
○ 2026-03-26 10:41:12
○A75.126.104.2282015-07-17 → 2016-01-12 · 5 obs
○ 2007-11-11 00:20:36
● 2015-07-17 05:27:06
● 2016-01-12 04:47:44
○ 2016-04-03 01:50:02
○ 2026-03-26 10:41:12
● 2015-07-17 05:27:06
● 2016-01-12 04:47:44
○ 2016-04-03 01:50:02
○ 2026-03-26 10:41:12
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| sinoengineers.com | launch2.spaceship.net, launch1.spaceship.net | - |
✅ Authoritative Response
Server:162.159.26.38
NS records: launch2.spaceship.net, launch1.spaceship.net
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 261ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 54.148.98.255 |
| NS | 2 | launch2.spaceship.net, launch1.spaceship.net |
| SOA | 1 | launch1.spaceship.net support.spaceship. |
Analysis
IP Addresses
sinoengineers.com resolves to one IP number: 54.148.98.255.
Other host names, for instance sinomineral.com, sinofiber.com, www.chinaautocontrols.com, sinopulp.com and sinotractors.com share IP numbers with sinoengineers.com.
Name Servers
sinoengineers.com's delegation uses two name servers: launch1.spaceship.net and launch2.spaceship.net.
sinoengineers.com uses the same name server setup as other domains, such as manfrotto.info, auburnparkelectrical.com, webzons.com, oklf.org and ivanhoe-band.com.
sinoengineers.com at least partially shares name servers with other domains, for example topicdirectory.com.
Host names with two IPs:
launch1.spaceship.net points to 2400:cb00:2049:1::a29f:1a26 and 162.159.26.38
launch2.spaceship.net points to 2400:cb00:2049:1::a29f:1b20 and 162.159.27.32