sailtag.com - robtex.com
sailtag.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns01.one.com ⚠️ Not in zone NS records | ||||||
| A | 2001:67c:28cc::10ONECOM-INFRA2001:67c:28cc::/48 | ||||||
| PTR | ns01.one.com | ||||||
| A | 195.206.121.10ONECOM-INFRA195.206.121.0/24 | ||||||
| PTR | ns01.one.com | ||||||
| NS | ns02.one.com ⚠️ Not in zone NS records | ||||||
| A | 2001:67c:3c0::10🇩🇰 ONECOM2001:67c:3c0::/48 | ||||||
| PTR | ns02.one.com | ||||||
| A | 185.10.11.10ONECOM185.10.11.0/24 | ||||||
| PTR | ns02.one.com | ||||||
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=1784846427 | ||||||
Same first word
sailtag.com |
Similar names
DNS History
16 records (2 active, 14 former)
○NSdns1.registrar-servers.com2015-06-18 → 2017-04-08 · 6 obs
● 2015-06-18 00:18:46
● 2016-01-16 01:19:06
○ 2016-04-08 13:27:16
● 2017-04-08 00:22:02
○ 2026-06-18 15:12:48
○ 2026-07-23 23:07:46
● 2016-01-16 01:19:06
○ 2016-04-08 13:27:16
● 2017-04-08 00:22:02
○ 2026-06-18 15:12:48
○ 2026-07-23 23:07:46
○NSdns1.registrar-servers.com,2016-04-08 → 2017-04-08 · 5 obs
○ 2016-01-16 01:19:06
● 2016-04-08 13:27:16
● 2017-04-08 00:22:02
○ 2026-06-18 15:12:48
○ 2026-07-23 23:07:46
● 2016-04-08 13:27:16
● 2017-04-08 00:22:02
○ 2026-06-18 15:12:48
○ 2026-07-23 23:07:46
○NSdns2.registrar-servers.com2015-06-18 → 2017-04-08 · 4 obs
● 2015-06-18 00:18:46
● 2017-04-08 00:22:02
○ 2026-06-18 15:12:48
○ 2026-07-23 23:07:46
● 2017-04-08 00:22:02
○ 2026-06-18 15:12:48
○ 2026-07-23 23:07:46
○NSdns3.registrar-servers.com2015-06-18 → 2017-04-08 · 4 obs
● 2015-06-18 00:18:46
● 2017-04-08 00:22:02
○ 2026-06-18 15:12:48
○ 2026-07-23 23:07:46
● 2017-04-08 00:22:02
○ 2026-06-18 15:12:48
○ 2026-07-23 23:07:46
○NSdns4.registrar-servers.com2015-06-18 → 2017-04-08 · 4 obs
● 2015-06-18 00:18:46
● 2017-04-08 00:22:02
○ 2026-06-18 15:12:48
○ 2026-07-23 23:07:46
● 2017-04-08 00:22:02
○ 2026-06-18 15:12:48
○ 2026-07-23 23:07:46
○NSdns5.registrar-servers.com2015-06-18 → 2017-04-08 · 4 obs
● 2015-06-18 00:18:46
● 2017-04-08 00:22:02
○ 2026-06-18 15:12:48
○ 2026-07-23 23:07:46
● 2017-04-08 00:22:02
○ 2026-06-18 15:12:48
○ 2026-07-23 23:07:46
●NSns01.one.com2026-06-18 → 2026-07-23 · 3 obs
○ 2017-04-08 00:22:02
● 2026-06-18 15:12:48
● 2026-07-23 23:07:46
● 2026-06-18 15:12:48
● 2026-07-23 23:07:46
●NSns02.one.com2026-06-18 → 2026-07-23 · 3 obs
○ 2017-04-08 00:22:02
● 2026-06-18 15:12:48
● 2026-07-23 23:07:46
● 2026-06-18 15:12:48
● 2026-07-23 23:07:46
○MXeforward1.registrar-servers.com2015-11-01 → 2017-04-08 · 4 obs
● 2015-11-01 07:23:18
● 2017-04-08 00:22:02
○ 2026-06-18 15:12:48
○ 2026-07-23 23:07:46
● 2017-04-08 00:22:02
○ 2026-06-18 15:12:48
○ 2026-07-23 23:07:46
○MXeforward2.registrar-servers.com2015-11-01 → 2017-04-08 · 4 obs
● 2015-11-01 07:23:18
● 2017-04-08 00:22:02
○ 2026-06-18 15:12:48
○ 2026-07-23 23:07:46
● 2017-04-08 00:22:02
○ 2026-06-18 15:12:48
○ 2026-07-23 23:07:46
○MXeforward3.registrar-servers.com2015-11-01 → 2017-04-08 · 4 obs
● 2015-11-01 07:23:18
● 2017-04-08 00:22:02
○ 2026-06-18 15:12:48
○ 2026-07-23 23:07:46
● 2017-04-08 00:22:02
○ 2026-06-18 15:12:48
○ 2026-07-23 23:07:46
○MXeforward4.registrar-servers.com2015-11-01 → 2017-04-08 · 4 obs
● 2015-11-01 07:23:18
● 2017-04-08 00:22:02
○ 2026-06-18 15:12:48
○ 2026-07-23 23:07:46
● 2017-04-08 00:22:02
○ 2026-06-18 15:12:48
○ 2026-07-23 23:07:46
○MXeforward5.registrar-servers.com2015-11-01 → 2017-04-08 · 4 obs
● 2015-11-01 07:23:18
● 2017-04-08 00:22:02
○ 2026-06-18 15:12:48
○ 2026-07-23 23:07:46
● 2017-04-08 00:22:02
○ 2026-06-18 15:12:48
○ 2026-07-23 23:07:46
○A162.255.119.2512016-01-16 → 2016-01-16 · 4 obs
○ 2015-11-01 07:23:18
● 2016-01-16 01:19:06
○ 2016-04-08 13:27:16
○ 2026-07-23 23:07:46
● 2016-01-16 01:19:06
○ 2016-04-08 13:27:16
○ 2026-07-23 23:07:46
○A192.64.119.2102016-04-08 → 2017-04-08 · 5 obs
○ 2016-01-16 01:19:06
● 2016-04-08 13:27:16
● 2017-04-08 00:22:02
○ 2026-06-18 15:12:48
○ 2026-07-23 23:07:46
● 2016-04-08 13:27:16
● 2017-04-08 00:22:02
○ 2026-06-18 15:12:48
○ 2026-07-23 23:07:46
○A192.64.119.812015-06-18 → 2015-11-01 · 4 obs
● 2015-06-18 00:18:46
● 2015-11-01 07:23:18
○ 2016-01-16 01:19:06
○ 2026-07-23 23:07:46
● 2015-11-01 07:23:18
○ 2016-01-16 01:19:06
○ 2026-07-23 23:07:46
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| sailtag.com | ns01.one.com, ns02.one.com | 4 records |
✅ Authoritative Response
Server:185.10.11.10
NS records: ns01.one.com, ns02.one.com
🔒 DNSSEC Status
❌ Bogus (DNSSEC validation failed)
No DNSKEY for sailtag.com
⏱️ Timing
Total: 315ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns01.one.com, ns01.one.com, ns02.one.com...)
Analysis
Name Servers
sailtag.com has two authoritative name servers — ns01.one.com and ns02.one.com.
sailtag.com has the same name server delegation as a number of other domains, such as formplus.se, markprodukter.com, aplung.se and two more.
Both ns01.one.com and ns02.one.com have two IP addresses each. ns01.one.com resolves to 195.206.121.10 and 2001:67c:28cc::10; ns02.one.com resolves to 185.10.11.10 and 2001:67c:3c0::10.