futuredebris.com - robtex.com
futuredebris.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 160.16.134.67🇯🇵 SAKURA-B160.16.128.0/17 (TOKYO) SAKURA Internet // EAST JAPAN BACKBONE Sakaisuji Honmachi Bldg. 9F 1-8-14 Minami-Honmachi, Chuo-ku Osaka 541-0054, Japan | ||||||
| PTR | tk2-403-42563.vs.sakura.ne.jp | ||||||
| NS | ns1.orchiddns.net ⭐ | ||||||
| A | 160.16.228.9🇯🇵 SAKURA-B160.16.128.0/17 (TOKYO) SAKURA Internet // EAST JAPAN BACKBONE Sakaisuji Honmachi Bldg. 9F 1-8-14 Minami-Honmachi, Chuo-ku Osaka 541-0054, Japan | ||||||
| PTR | tk2-256-37505.vs.sakura.ne.jp | ||||||
| NS | ns2.orchiddns.net | ||||||
| A | 153.126.157.236🇯🇵 SAKURA-A153.126.128.0/17 (ISHIKARI) SAKURA Internet // HOKKAIDO JAPAN BACKBONE Sakaisuji Honmachi Bldg. 9F 1-8-14 Minami-Honmachi, Chuo-ku Osaka 541-0054, Japan | ||||||
| PTR | ik1-314-17482.vs.sakura.ne.jp | ||||||
| SOA | ns1.orchiddns.netadmin@futuredebris.com serial=1577239622 | ||||||
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=1778548202 | ||||||
Same first word
futuredebris.com |
DNS History
16 records (3 active, 13 former)
○NSdns1.p01.nsone.net2017-02-01 → 2017-02-01 · 4 obs
○ 2016-05-07 13:22:02
● 2017-02-01 00:19:06
○ 2018-06-23 10:48:48
○ 2026-05-12 01:15:28
● 2017-02-01 00:19:06
○ 2018-06-23 10:48:48
○ 2026-05-12 01:15:28
○NSdns2.p01.nsone.net2017-02-01 → 2017-02-01 · 4 obs
○ 2016-05-07 13:22:02
● 2017-02-01 00:19:06
○ 2018-06-23 10:48:48
○ 2026-05-12 01:15:28
● 2017-02-01 00:19:06
○ 2018-06-23 10:48:48
○ 2026-05-12 01:15:28
○NSdns3.p01.nsone.net2017-02-01 → 2017-02-01 · 4 obs
○ 2016-05-07 13:22:02
● 2017-02-01 00:19:06
○ 2018-06-23 10:48:48
○ 2026-05-12 01:15:28
● 2017-02-01 00:19:06
○ 2018-06-23 10:48:48
○ 2026-05-12 01:15:28
○NSdns4.p01.nsone.net2017-02-01 → 2017-02-01 · 4 obs
○ 2016-05-07 13:22:02
● 2017-02-01 00:19:06
○ 2018-06-23 10:48:48
○ 2026-05-12 01:15:28
● 2017-02-01 00:19:06
○ 2018-06-23 10:48:48
○ 2026-05-12 01:15:28
●NSns1.orchiddns.net2026-03-25 → 2026-05-12 · 3 obs
○ 2018-06-23 10:48:48
● 2026-03-25 16:39:22
● 2026-05-12 01:15:28
● 2026-03-25 16:39:22
● 2026-05-12 01:15:28
○NSns1.systemdns.com2015-07-25 → 2016-05-07 · 4 obs
● 2015-07-25 16:12:42
● 2016-05-07 13:22:02
○ 2017-02-01 00:19:06
○ 2026-05-12 01:15:28
● 2016-05-07 13:22:02
○ 2017-02-01 00:19:06
○ 2026-05-12 01:15:28
●NSns2.orchiddns.net2026-03-25 → 2026-05-12 · 3 obs
○ 2018-06-23 10:48:48
● 2026-03-25 16:39:22
● 2026-05-12 01:15:28
● 2026-03-25 16:39:22
● 2026-05-12 01:15:28
○NSns2.systemdns.com2015-07-25 → 2016-05-07 · 4 obs
● 2015-07-25 16:12:42
● 2016-05-07 13:22:02
○ 2017-02-01 00:19:06
○ 2026-05-12 01:15:28
● 2016-05-07 13:22:02
○ 2017-02-01 00:19:06
○ 2026-05-12 01:15:28
○NSns3.systemdns.com2015-07-25 → 2016-05-07 · 4 obs
● 2015-07-25 16:12:42
● 2016-05-07 13:22:02
○ 2017-02-01 00:19:06
○ 2026-05-12 01:15:28
● 2016-05-07 13:22:02
○ 2017-02-01 00:19:06
○ 2026-05-12 01:15:28
○NSns5.2kz.net2018-06-23 → 2018-06-23 · 4 obs
○ 2017-02-01 00:19:06
● 2018-06-23 10:48:48
○ 2026-03-25 16:39:22
○ 2026-05-12 01:15:28
● 2018-06-23 10:48:48
○ 2026-03-25 16:39:22
○ 2026-05-12 01:15:28
○NSns6.2kz.net2018-06-23 → 2018-06-23 · 4 obs
○ 2017-02-01 00:19:06
● 2018-06-23 10:48:48
○ 2026-03-25 16:39:22
○ 2026-05-12 01:15:28
● 2018-06-23 10:48:48
○ 2026-03-25 16:39:22
○ 2026-05-12 01:15:28
○NSns7.2kz.net2018-06-23 → 2018-06-23 · 4 obs
○ 2017-02-01 00:19:06
● 2018-06-23 10:48:48
○ 2026-03-25 16:39:22
○ 2026-05-12 01:15:28
● 2018-06-23 10:48:48
○ 2026-03-25 16:39:22
○ 2026-05-12 01:15:28
○NSns8.2kz.net2018-06-23 → 2018-06-23 · 4 obs
○ 2017-02-01 00:19:06
● 2018-06-23 10:48:48
○ 2026-03-25 16:39:22
○ 2026-05-12 01:15:28
● 2018-06-23 10:48:48
○ 2026-03-25 16:39:22
○ 2026-05-12 01:15:28
○A107.187.129.2322018-06-23 → 2018-06-23 · 4 obs
○ 2017-02-01 00:19:06
● 2018-06-23 10:48:48
○ 2026-03-25 16:39:22
○ 2026-05-12 01:15:28
● 2018-06-23 10:48:48
○ 2026-03-25 16:39:22
○ 2026-05-12 01:15:28
●A160.16.134.672026-03-25 → 2026-05-12 · 3 obs
○ 2018-06-23 10:48:48
● 2026-03-25 16:39:22
● 2026-05-12 01:15:28
● 2026-03-25 16:39:22
● 2026-05-12 01:15:28
○A198.185.159.1442015-07-25 → 2017-02-01 · 4 obs
● 2015-07-25 16:12:42
● 2017-02-01 00:19:06
○ 2018-06-23 10:48:48
○ 2026-05-12 01:15:28
● 2017-02-01 00:19:06
○ 2018-06-23 10:48:48
○ 2026-05-12 01:15:28
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| futuredebris.com | ns1.orchiddns.net, ns2.orchiddns.net | - |
✅ Authoritative Response
Server:153.126.157.236
NS records: ns1.orchiddns.net, ns2.orchiddns.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for futuredebris.com (unsigned zone)
⏱️ Timing
Total: 2094ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 160.16.134.67 |
| NS | 2 | ns1.orchiddns.net, ns2.orchiddns.net |
| SOA | 1 | ns1.orchiddns.net admin.futuredebris.com |
Analysis
IP Addresses
futuredebris.com points to a single IP address: 160.16.134.67.
Other host names, for instance samirworld.com, tk2-403-42563.vs.sakura.ne.jp, parentcontrol.biz and kartene.info share IP numbers with futuredebris.com.
Name Servers
futuredebris.com is delegated to two name servers: ns1.orchiddns.net and ns2.orchiddns.net.
futuredebris.com uses the same name server setup as other domains, including hae-network.info, svyato.biz, screen-mates.com, program-trends.com and outdoor-boriscompany.com.
Hostnames with a single IP
ns1.orchiddns.net resolves to: 160.16.228.9.
ns2.orchiddns.net resolves to: 153.126.157.236.