miretsurgical.com - robtex.com
miretsurgical.com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| A | 34.216.117.25🇺🇸 Amazon34.208.0.0/12 EC2 PDX prefix | ||||||
| PTR | ec2-34-216-117-25.us-west-2.compute.amazonaws.com | ||||||
| A | 54.149.79.189🇺🇸 Amazon54.148.0.0/15 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=1754885684 | ||||||
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=1785082432 | ||||||
Same first word
miretsurgical.com |
Similar names
DNS History
22 records (4 active, 18 former)
●NSlaunch1.spaceship.net2026-07-01 → 2026-07-26 · 3 obs
● 2026-07-01 05:10:16
● 2026-07-26 16:40:58
●NSlaunch2.spaceship.net2026-07-01 → 2026-07-26 · 3 obs
● 2026-07-01 05:10:16
● 2026-07-26 16:40:58
○NSns1.dnsimple.com2016-11-23 → 2017-09-24 · 5 obs
● 2016-11-23 12:11:38
● 2017-09-24 19:46:40
○ 2026-07-01 05:10:16
○ 2026-07-26 16:40:58
○NSns1.pipedns.com2015-06-02 → 2016-04-09 · 4 obs
● 2016-04-09 16:38:06
○ 2016-11-23 12:11:38
○ 2026-07-26 16:40:58
○NSns2.dnsimple.com2016-11-23 → 2017-09-24 · 5 obs
● 2016-11-23 12:11:38
● 2017-09-24 19:46:40
○ 2026-07-01 05:10:16
○ 2026-07-26 16:40:58
○NSns2.pipedns.com2015-06-02 → 2016-04-09 · 4 obs
● 2016-04-09 16:38:06
○ 2016-11-23 12:11:38
○ 2026-07-26 16:40:58
○NSns3.dnsimple.com2016-11-23 → 2017-09-24 · 5 obs
● 2016-11-23 12:11:38
● 2017-09-24 19:46:40
○ 2026-07-01 05:10:16
○ 2026-07-26 16:40:58
○NSns3.pipedns.com2015-06-02 → 2016-04-09 · 4 obs
● 2016-04-09 16:38:06
○ 2016-11-23 12:11:38
○ 2026-07-26 16:40:58
○NSns4.dnsimple.com2016-11-23 → 2017-09-24 · 5 obs
● 2016-11-23 12:11:38
● 2017-09-24 19:46:40
○ 2026-07-01 05:10:16
○ 2026-07-26 16:40:58
○MXalt1.aspmx.l.google.com2015-06-02 → 2017-09-24 · 4 obs
● 2017-09-24 19:46:40
○ 2026-07-01 05:10:16
○ 2026-07-26 16:40:58
○MXalt2.aspmx.l.google.com2015-06-02 → 2017-09-24 · 4 obs
● 2017-09-24 19:46:40
○ 2026-07-01 05:10:16
○ 2026-07-26 16:40:58
○MXalt3.aspmx.l.google.com2016-11-23 → 2017-09-24 · 5 obs
● 2016-11-23 12:11:38
● 2017-09-24 19:46:40
○ 2026-07-01 05:10:16
○ 2026-07-26 16:40:58
○MXalt4.aspmx.l.google.com2016-11-23 → 2017-09-24 · 5 obs
● 2016-11-23 12:11:38
● 2017-09-24 19:46:40
○ 2026-07-01 05:10:16
○ 2026-07-26 16:40:58
○MXaspmx.l.google.com2015-06-02 → 2017-09-24 · 4 obs
● 2017-09-24 19:46:40
○ 2026-07-01 05:10:16
○ 2026-07-26 16:40:58
○MXaspmx2.googlemail.com2015-06-02 → 2016-04-09 · 4 obs
● 2016-04-09 16:38:06
○ 2016-11-23 12:11:38
○ 2026-07-26 16:40:58
○MXaspmx3.googlemail.com2015-06-02 → 2016-04-09 · 4 obs
● 2016-04-09 16:38:06
○ 2016-11-23 12:11:38
○ 2026-07-26 16:40:58
○MXaspmx4.googlemail.com2015-06-02 → 2016-04-09 · 4 obs
● 2016-04-09 16:38:06
○ 2016-11-23 12:11:38
○ 2026-07-26 16:40:58
○MXaspmx5.googlemail.com2015-06-02 → 2016-04-09 · 4 obs
● 2016-04-09 16:38:06
○ 2016-11-23 12:11:38
○ 2026-07-26 16:40:58
○A173.254.28.892015-06-02 → 2017-09-24 · 6 obs
● 2016-04-09 16:38:06
○ 2016-11-23 12:11:38
● 2017-09-24 19:46:40
○ 2026-07-01 05:10:16
○ 2026-07-26 16:40:58
●A34.216.117.252026-07-01 → 2026-07-26 · 4 obs
● 2026-07-01 05:10:16
○ 2026-07-23 20:07:46
● 2026-07-26 16:40:58
○A50.31.225.932016-11-23 → 2016-11-23 · 4 obs
● 2016-11-23 12:11:38
○ 2017-09-24 19:46:40
○ 2026-07-26 16:40:58
●A54.149.79.1892026-07-01 → 2026-07-26 · 4 obs
● 2026-07-01 05:10:16
○ 2026-07-23 20:07:46
● 2026-07-26 16:40:58
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | d.gtld-servers.net, a.gtld-servers.net, b.gtld-servers.net, f.gtld-servers.net... | - |
| miretsurgical.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: 273ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 54.149.79.189, 34.216.117.25 |
| NS | 2 | launch1.spaceship.net, launch2.spaceship.net |
| SOA | 1 | launch1.spaceship.net support.spaceship. |
Analysis
IP Addresses
miretsurgical.com directs to two IP numbers, 34.216.117.25 and 54.149.79.189
Additional host names — sicular.net, weabi.com, livelyadvisor.com and two others — share IP numbers with miretsurgical.com.
Name Servers
miretsurgical.com has two authoritative name servers — launch1.spaceship.net and launch2.spaceship.net.
miretsurgical.com shares its name server setup with other domains, including sorayaa.com, 10.cm, hffd.com and two others.
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.