bindik.com - dns.ninja
bindik.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 208.91.197.39🇻🇬 CONFLUENCE-NETWORK-INC208.91.197.0/24 Confluence Networks Route Object | ||||||
| NS | dns101.register.com ⭐ | ||||||
| A | 162.159.24.117Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | dns102.register.com | ||||||
| A | 162.159.25.158Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| SOA | DNS101.REGISTER.comroot@REGISTER.com serial=121010408 | ||||||
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=1783844937 | ||||||
Same first word
Similar names
kinibd.com |
bdkini.com |
kibind.com |
bidink.com |
kibind.com.ar |
kindbi.ru |
kindbi.com |
ikbind.com |
kidbin.com |
bidnik.com |
kinbid.com |
inkbid.com |
binkid.com |
DNS History
14 records (3 active, 11 former)
○NSdns084.a.register.com2015-06-15 → 2016-08-21 · 7 obs
● 2015-06-15 15:11:02
● 2016-04-20 08:17:58
○ 2016-07-17 02:04:20
● 2016-07-31 18:32:12
● 2016-08-21 23:17:30
○ 2017-08-24 09:41:22
○ 2026-07-12 08:50:54
● 2016-04-20 08:17:58
○ 2016-07-17 02:04:20
● 2016-07-31 18:32:12
● 2016-08-21 23:17:30
○ 2017-08-24 09:41:22
○ 2026-07-12 08:50:54
○NSdns099.b.register.com2015-06-15 → 2016-08-21 · 7 obs
● 2015-06-15 15:11:02
● 2016-04-20 08:17:58
○ 2016-07-17 02:04:20
● 2016-07-31 18:32:12
● 2016-08-21 23:17:30
○ 2017-08-24 09:41:22
○ 2026-07-12 08:50:54
● 2016-04-20 08:17:58
○ 2016-07-17 02:04:20
● 2016-07-31 18:32:12
● 2016-08-21 23:17:30
○ 2017-08-24 09:41:22
○ 2026-07-12 08:50:54
●NSdns101.register.com2026-04-07 → 2026-07-12 · 3 obs
○ 2017-08-24 09:41:22
● 2026-04-07 10:15:58
● 2026-07-12 08:50:54
● 2026-04-07 10:15:58
● 2026-07-12 08:50:54
●NSdns102.register.com2026-04-07 → 2026-07-12 · 3 obs
○ 2017-08-24 09:41:22
● 2026-04-07 10:15:58
● 2026-07-12 08:50:54
● 2026-04-07 10:15:58
● 2026-07-12 08:50:54
○NSdns206.c.register.com2015-06-15 → 2016-08-21 · 7 obs
● 2015-06-15 15:11:02
● 2016-04-20 08:17:58
○ 2016-07-17 02:04:20
● 2016-07-31 18:32:12
● 2016-08-21 23:17:30
○ 2017-08-24 09:41:22
○ 2026-07-12 08:50:54
● 2016-04-20 08:17:58
○ 2016-07-17 02:04:20
● 2016-07-31 18:32:12
● 2016-08-21 23:17:30
○ 2017-08-24 09:41:22
○ 2026-07-12 08:50:54
○NSdns249.d.register.com2015-06-15 → 2016-08-21 · 7 obs
● 2015-06-15 15:11:02
● 2016-04-20 08:17:58
○ 2016-07-17 02:04:20
● 2016-07-31 18:32:12
● 2016-08-21 23:17:30
○ 2017-08-24 09:41:22
○ 2026-07-12 08:50:54
● 2016-04-20 08:17:58
○ 2016-07-17 02:04:20
● 2016-07-31 18:32:12
● 2016-08-21 23:17:30
○ 2017-08-24 09:41:22
○ 2026-07-12 08:50:54
○NSsk.s5.ans1.ns122.ztomy.com2016-07-17 → 2017-08-24 · 7 obs
○ 2016-04-20 08:17:58
● 2016-07-17 02:04:20
○ 2016-07-31 18:32:12
○ 2016-08-21 23:17:30
● 2017-08-24 09:41:22
○ 2026-04-07 10:15:58
○ 2026-07-12 08:50:54
● 2016-07-17 02:04:20
○ 2016-07-31 18:32:12
○ 2016-08-21 23:17:30
● 2017-08-24 09:41:22
○ 2026-04-07 10:15:58
○ 2026-07-12 08:50:54
○NSsk.s5.ans2.ns122.ztomy.com2016-07-17 → 2017-08-24 · 7 obs
○ 2016-04-20 08:17:58
● 2016-07-17 02:04:20
○ 2016-07-31 18:32:12
○ 2016-08-21 23:17:30
● 2017-08-24 09:41:22
○ 2026-04-07 10:15:58
○ 2026-07-12 08:50:54
● 2016-07-17 02:04:20
○ 2016-07-31 18:32:12
○ 2016-08-21 23:17:30
● 2017-08-24 09:41:22
○ 2026-04-07 10:15:58
○ 2026-07-12 08:50:54
○MXmail.hope-mail.com2017-08-24 → 2017-08-24 · 4 obs
○ 2016-08-21 23:17:30
● 2017-08-24 09:41:22
○ 2026-04-07 10:15:58
○ 2026-07-12 08:50:54
● 2017-08-24 09:41:22
○ 2026-04-07 10:15:58
○ 2026-07-12 08:50:54
○MXp.webcom.ctmail.com2016-04-20 → 2016-08-21 · 6 obs
● 2016-04-20 08:17:58
○ 2016-07-17 02:04:20
● 2016-07-31 18:32:12
● 2016-08-21 23:17:30
○ 2017-08-24 09:41:22
○ 2026-07-12 08:50:54
○ 2016-07-17 02:04:20
● 2016-07-31 18:32:12
● 2016-08-21 23:17:30
○ 2017-08-24 09:41:22
○ 2026-07-12 08:50:54
●A208.91.197.392026-04-07 → 2026-07-12 · 3 obs
○ 2017-08-24 09:41:22
● 2026-04-07 10:15:58
● 2026-07-12 08:50:54
● 2026-04-07 10:15:58
● 2026-07-12 08:50:54
○A208.91.197.442016-07-17 → 2017-08-24 · 7 obs
○ 2016-04-20 08:17:58
● 2016-07-17 02:04:20
○ 2016-07-31 18:32:12
○ 2016-08-21 23:17:30
● 2017-08-24 09:41:22
○ 2026-04-07 10:15:58
○ 2026-07-12 08:50:54
● 2016-07-17 02:04:20
○ 2016-07-31 18:32:12
○ 2016-08-21 23:17:30
● 2017-08-24 09:41:22
○ 2026-04-07 10:15:58
○ 2026-07-12 08:50:54
○A216.21.239.1972015-06-15 → 2016-08-21 · 7 obs
● 2015-06-15 15:11:02
● 2016-04-20 08:17:58
○ 2016-07-17 02:04:20
● 2016-07-31 18:32:12
● 2016-08-21 23:17:30
○ 2017-08-24 09:41:22
○ 2026-07-12 08:50:54
● 2016-04-20 08:17:58
○ 2016-07-17 02:04:20
● 2016-07-31 18:32:12
● 2016-08-21 23:17:30
○ 2017-08-24 09:41:22
○ 2026-07-12 08:50:54
○PTRsk.s5.ans1.ns122.ztomy.com2017-08-24 → 2017-08-24 · 3 obs
● 2017-08-24 09:41:22
○ 2026-04-07 10:15:58
○ 2026-07-12 08:50:54
○ 2026-04-07 10:15:58
○ 2026-07-12 08:50:54
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | c.gtld-servers.net, k.gtld-servers.net, a.gtld-servers.net, m.gtld-servers.net... | - |
| bindik.com | dns101.register.com, dns102.register.com | 2 records |
✅ Authoritative Response
Server:162.159.24.117
NS records: dns101.register.com, dns102.register.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for bindik.com (unsigned zone)
⏱️ Timing
Total: 184ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 208.91.197.39 |
| NS | 2 | dns102.register.com, dns101.register.com |
| SOA | 1 | DNS101.REGISTER.com root.REGISTER.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (dns101.register.com, dns102.register.com)
Analysis
IP Addresses
bindik.com resolves to one IP address: 208.91.197.39.
angeloapostolou.com, polkadotpics.com, rhdconversionguide.doodlekit.com and two other host names share IP numbers with bindik.com.
Name Servers
bindik.com has two authoritative name servers — dns101.register.com and dns102.register.com.
bindik.com uses the same name servers as several other domains — among them ipankey.com, yannett.com, circuitrage.com and two more.
The name servers for bindik.com overlap at least partially with those of other domains — for example yaleclubdc.org.
dns101.register.com resolves to 162.159.24.117. dns102.register.com resolves to 162.159.25.158. Both host names point to a single IP number.