bmtcl.com - dns.ninja
bmtcl.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 183.136.138.174🇨🇳 CHINATELECOM-ZHEJIANG-NINGBO-IDC183.136.138.0/24 Chinanet-NingBo-IDC | ||||||
| NS | ns1.julydns.com ⭐ | ||||||
| A | 162.159.48.223Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | ns2.julydns.com | ||||||
| A | 162.159.48.223Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| SOA | ns1.julydns.commaster@jmdns.com serial=1784362828 | ||||||
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=1786274119 | ||||||
Same first word
bmtcl.com |
Similar names
DNS History
23 records (3 active, 20 former)
○NSamit.ns.cloudflare.com2026-02-18 → 2026-04-06 · 5 obs
○ 2019-12-30 14:10:44
● 2026-02-18 23:11:10
● 2026-04-06 10:57:06
○ 2026-04-17 04:57:40
○ 2026-08-09 11:28:06
● 2026-02-18 23:11:10
● 2026-04-06 10:57:06
○ 2026-04-17 04:57:40
○ 2026-08-09 11:28:06
○NSbeth.ns.cloudflare.com2026-02-18 → 2026-04-06 · 5 obs
○ 2019-12-30 14:10:44
● 2026-02-18 23:11:10
● 2026-04-06 10:57:06
○ 2026-04-17 04:57:40
○ 2026-08-09 11:28:06
● 2026-02-18 23:11:10
● 2026-04-06 10:57:06
○ 2026-04-17 04:57:40
○ 2026-08-09 11:28:06
○NSdns15.hichina.com2015-06-09 → 2019-12-30 · 4 obs
● 2015-06-09 11:45:32
● 2019-12-30 14:10:44
○ 2026-02-18 23:11:10
○ 2026-08-09 11:28:06
● 2019-12-30 14:10:44
○ 2026-02-18 23:11:10
○ 2026-08-09 11:28:06
○NSdns16.hichina.com2015-06-09 → 2019-12-30 · 4 obs
● 2015-06-09 11:45:32
● 2019-12-30 14:10:44
○ 2026-02-18 23:11:10
○ 2026-08-09 11:28:06
● 2019-12-30 14:10:44
○ 2026-02-18 23:11:10
○ 2026-08-09 11:28:06
○NSexpire1.gname-dns.com2026-04-17 → 2026-04-29 · 5 obs
○ 2026-04-06 10:57:06
● 2026-04-17 04:57:40
● 2026-04-29 10:26:36
○ 2026-05-05 14:19:22
○ 2026-08-09 11:28:06
● 2026-04-17 04:57:40
● 2026-04-29 10:26:36
○ 2026-05-05 14:19:22
○ 2026-08-09 11:28:06
○NSexpire2.gname-dns.com2026-04-17 → 2026-04-29 · 5 obs
○ 2026-04-06 10:57:06
● 2026-04-17 04:57:40
● 2026-04-29 10:26:36
○ 2026-05-05 14:19:22
○ 2026-08-09 11:28:06
● 2026-04-17 04:57:40
● 2026-04-29 10:26:36
○ 2026-05-05 14:19:22
○ 2026-08-09 11:28:06
●NSns1.julydns.com2026-05-12 → 2026-08-09 · 3 obs
○ 2026-05-05 14:19:22
● 2026-05-12 17:05:48
● 2026-08-09 11:28:06
● 2026-05-12 17:05:48
● 2026-08-09 11:28:06
●NSns2.julydns.com2026-05-12 → 2026-08-09 · 3 obs
○ 2026-05-05 14:19:22
● 2026-05-12 17:05:48
● 2026-08-09 11:28:06
● 2026-05-12 17:05:48
● 2026-08-09 11:28:06
○NSsp1.gname-dns.com2026-05-05 → 2026-05-05 · 4 obs
○ 2026-04-29 10:26:36
● 2026-05-05 14:19:22
○ 2026-05-12 17:05:48
○ 2026-08-09 11:28:06
● 2026-05-05 14:19:22
○ 2026-05-12 17:05:48
○ 2026-08-09 11:28:06
○NSsp2.gname-dns.com2026-05-05 → 2026-05-05 · 4 obs
○ 2026-04-29 10:26:36
● 2026-05-05 14:19:22
○ 2026-05-12 17:05:48
○ 2026-08-09 11:28:06
● 2026-05-05 14:19:22
○ 2026-05-12 17:05:48
○ 2026-08-09 11:28:06
○A104.21.20.122026-02-18 → 2026-04-06 · 5 obs
○ 2019-12-30 14:10:44
● 2026-02-18 23:11:10
● 2026-04-06 10:57:06
○ 2026-04-17 04:57:40
○ 2026-08-09 11:28:06
● 2026-02-18 23:11:10
● 2026-04-06 10:57:06
○ 2026-04-17 04:57:40
○ 2026-08-09 11:28:06
○A112.126.244.1552015-06-09 → 2016-07-10 · 4 obs
● 2015-06-09 11:45:32
● 2016-07-10 10:06:36
○ 2017-03-15 01:37:40
○ 2026-08-09 11:28:06
● 2016-07-10 10:06:36
○ 2017-03-15 01:37:40
○ 2026-08-09 11:28:06
○A172.67.190.1972026-02-18 → 2026-04-06 · 5 obs
○ 2019-12-30 14:10:44
● 2026-02-18 23:11:10
● 2026-04-06 10:57:06
○ 2026-04-17 04:57:40
○ 2026-08-09 11:28:06
● 2026-02-18 23:11:10
● 2026-04-06 10:57:06
○ 2026-04-17 04:57:40
○ 2026-08-09 11:28:06
●A183.136.138.1742026-05-24 → 2026-08-09 · 3 obs
○ 2026-04-17 04:57:40
● 2026-05-24 11:01:20
● 2026-08-09 11:28:06
● 2026-05-24 11:01:20
● 2026-08-09 11:28:06
○A220.181.112.782017-03-15 → 2017-03-15 · 4 obs
○ 2016-07-10 10:06:36
● 2017-03-15 01:37:40
○ 2019-12-30 14:10:44
○ 2026-08-09 11:28:06
● 2017-03-15 01:37:40
○ 2019-12-30 14:10:44
○ 2026-08-09 11:28:06
○A220.181.112.812017-03-15 → 2017-03-15 · 4 obs
○ 2016-07-10 10:06:36
● 2017-03-15 01:37:40
○ 2019-12-30 14:10:44
○ 2026-08-09 11:28:06
● 2017-03-15 01:37:40
○ 2019-12-30 14:10:44
○ 2026-08-09 11:28:06
○A2606:4700:3031::ac43:bec52026-02-18 → 2026-04-06 · 5 obs
○ 2019-12-30 14:10:44
● 2026-02-18 23:11:10
● 2026-04-06 10:57:06
○ 2026-04-17 04:57:40
○ 2026-08-09 11:28:06
● 2026-02-18 23:11:10
● 2026-04-06 10:57:06
○ 2026-04-17 04:57:40
○ 2026-08-09 11:28:06
○A2606:4700:3032::6815:140c2026-02-18 → 2026-04-06 · 5 obs
○ 2019-12-30 14:10:44
● 2026-02-18 23:11:10
● 2026-04-06 10:57:06
○ 2026-04-17 04:57:40
○ 2026-08-09 11:28:06
● 2026-02-18 23:11:10
● 2026-04-06 10:57:06
○ 2026-04-17 04:57:40
○ 2026-08-09 11:28:06
○CNAMEbdysite.n.shifen.com2017-03-15 → 2017-03-15 · 3 obs
● 2017-03-15 01:37:40
○ 2019-12-30 14:10:44
○ 2026-08-09 11:28:06
○ 2019-12-30 14:10:44
○ 2026-08-09 11:28:06
○CNAMEexp.gname.net2026-04-24 → 2026-04-29 · 5 obs
○ 2026-04-17 04:57:40
● 2026-04-24 16:35:24
● 2026-04-29 10:26:36
○ 2026-05-05 14:19:22
○ 2026-08-09 11:28:06
● 2026-04-24 16:35:24
● 2026-04-29 10:26:36
○ 2026-05-05 14:19:22
○ 2026-08-09 11:28:06
○CNAMEexp.gs-cdn.com2026-04-17 → 2026-04-17 · 4 obs
○ 2026-02-18 23:11:10
● 2026-04-17 04:57:40
○ 2026-04-24 16:35:24
○ 2026-08-09 11:28:06
● 2026-04-17 04:57:40
○ 2026-04-24 16:35:24
○ 2026-08-09 11:28:06
○CNAMEsp.gname.net2026-05-05 → 2026-05-05 · 4 obs
○ 2026-04-29 10:26:36
● 2026-05-05 14:19:22
○ 2026-05-12 17:05:48
○ 2026-08-09 11:28:06
● 2026-05-05 14:19:22
○ 2026-05-12 17:05:48
○ 2026-08-09 11:28:06
○CNAMEsy002243.fc.bdysite.com2017-03-15 → 2019-12-30 · 4 obs
● 2017-03-15 01:37:40
● 2019-12-30 14:10:44
○ 2026-02-18 23:11:10
○ 2026-08-09 11:28:06
● 2019-12-30 14:10:44
○ 2026-02-18 23:11:10
○ 2026-08-09 11:28:06
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| bmtcl.com | ns1.julydns.com, ns2.julydns.com | 2 records |
✅ Authoritative Response
Server:162.159.48.223
NS records: ns1.julydns.com, ns2.julydns.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for bmtcl.com (unsigned zone)
⏱️ Timing
Total: 453ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 183.136.138.174 |
| NS | 2 | ns1.julydns.com, ns2.julydns.com |
| SOA | 1 | ns1.julydns.com master.jmdns.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.julydns.com, ns2.julydns.com)
Analysis
IP Addresses
bmtcl.com resolves to just one IP address, 183.136.138.174.
Two other host names, along with enlxcof.com, ausdrhs.com and pop-jiafang.com, also share IP numbers with bmtcl.com.
Name Servers
The NS records for bmtcl.com delegate to ns1.julydns.com and ns2.julydns.com.
bmtcl.com shares its NS records with other domains, for example jygwlzx.com, daliantg.com, liuquzhihui.com and two others.
bmtcl.com has at least partial name server overlap with other domains, such as bsjfs.com, bjsjh.com, murnz.cn and two others.
It is common to find these name servers paired with the name servers ns1.judns.com, ns2.judns.com, ns1.onclouddns.com and ns2.onclouddns.com.
Each of ns1.julydns.com and ns2.julydns.com points to exactly one IP address: 162.159.48.223.
ns1.julydns.com and ns2.julydns.com each have 162.159.48.223 IP addresses.