sm021.com - dns.ninja
sm021.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.kouming.net ⭐ ⚠️ Not in zone NS records | ||||||
| A | 2610:150:c011:5:1::101🇺🇸 SHARKTECH-12610:150:c000::/34 Sharktech Inc. | ||||||
| A | 64.32.22.243🇺🇸 SHARKTECH-164.32.22.0/24 CMI (Customer Route) | ||||||
| PTR | qualidade-243-22-32-64.valeapenater.com.br | ||||||
| NS | ns2.kouming.net ⚠️ Not in zone NS records | ||||||
| A | 2400:ede0:8000:1::5🇭🇰 HKKF-12400:ede0::/32 client's prefix | ||||||
| A | 103.97.0.246🇭🇰 SZKF-AS-AP103.97.0.0/24 HKKF | ||||||
| SOA | ns1.kouming.netroot@kouming.net serial=1784663767 | ||||||
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=1785887014 | ||||||
Same first word
Similar names
DNS History
11 records (2 active, 9 former)
○NSf1g1ns1.dnspod.net2016-06-30 → 2018-08-20 · 4 obs
● 2016-06-30 05:36:26
● 2018-08-20 17:21:20
○ 2026-02-28 03:29:28
○ 2026-08-04 23:53:00
● 2018-08-20 17:21:20
○ 2026-02-28 03:29:28
○ 2026-08-04 23:53:00
○NSf1g1ns2.dnspod.net2016-06-30 → 2018-08-20 · 4 obs
● 2016-06-30 05:36:26
● 2018-08-20 17:21:20
○ 2026-02-28 03:29:28
○ 2026-08-04 23:53:00
● 2018-08-20 17:21:20
○ 2026-02-28 03:29:28
○ 2026-08-04 23:53:00
○NSns1.domainnamedns.com2026-02-28 → 2026-04-04 · 5 obs
○ 2018-08-20 17:21:20
● 2026-02-28 03:29:28
● 2026-04-04 14:51:26
○ 2026-07-13 20:32:10
○ 2026-08-04 23:53:00
● 2026-02-28 03:29:28
● 2026-04-04 14:51:26
○ 2026-07-13 20:32:10
○ 2026-08-04 23:53:00
●NSns1.kouming.net2026-07-31 → 2026-08-04 · 3 obs
○ 2026-07-13 20:32:10
● 2026-07-31 01:49:42
● 2026-08-04 23:53:00
● 2026-07-31 01:49:42
● 2026-08-04 23:53:00
○NSns2.domainnamedns.com2026-02-28 → 2026-04-04 · 5 obs
○ 2018-08-20 17:21:20
● 2026-02-28 03:29:28
● 2026-04-04 14:51:26
○ 2026-07-13 20:32:10
○ 2026-08-04 23:53:00
● 2026-02-28 03:29:28
● 2026-04-04 14:51:26
○ 2026-07-13 20:32:10
○ 2026-08-04 23:53:00
●NSns2.kouming.net2026-07-31 → 2026-08-04 · 3 obs
○ 2026-07-13 20:32:10
● 2026-07-31 01:49:42
● 2026-08-04 23:53:00
● 2026-07-31 01:49:42
● 2026-08-04 23:53:00
○NSns3.domainnamedns.com2026-02-28 → 2026-04-04 · 5 obs
○ 2018-08-20 17:21:20
● 2026-02-28 03:29:28
● 2026-04-04 14:51:26
○ 2026-07-13 20:32:10
○ 2026-08-04 23:53:00
● 2026-02-28 03:29:28
● 2026-04-04 14:51:26
○ 2026-07-13 20:32:10
○ 2026-08-04 23:53:00
○NSns4.domainnamedns.com2026-02-28 → 2026-04-04 · 5 obs
○ 2018-08-20 17:21:20
● 2026-02-28 03:29:28
● 2026-04-04 14:51:26
○ 2026-07-13 20:32:10
○ 2026-08-04 23:53:00
● 2026-02-28 03:29:28
● 2026-04-04 14:51:26
○ 2026-07-13 20:32:10
○ 2026-08-04 23:53:00
○A154.205.76.1172026-02-28 → 2026-04-04 · 5 obs
○ 2017-10-13 21:11:18
● 2026-02-28 03:29:28
● 2026-04-04 14:51:26
○ 2026-07-13 20:32:10
○ 2026-08-04 23:53:00
● 2026-02-28 03:29:28
● 2026-04-04 14:51:26
○ 2026-07-13 20:32:10
○ 2026-08-04 23:53:00
○A222.76.215.492016-06-30 → 2017-03-15 · 4 obs
● 2016-06-30 05:36:26
● 2017-03-15 16:26:46
○ 2017-10-13 21:11:18
○ 2026-08-04 23:53:00
● 2017-03-15 16:26:46
○ 2017-10-13 21:11:18
○ 2026-08-04 23:53:00
○CNAMEedjs02pos.w267-e0.ezcname.com2017-10-13 → 2018-08-20 · 4 obs
● 2017-10-13 21:11:18
● 2018-08-20 17:21:20
○ 2026-02-28 03:29:28
○ 2026-08-04 23:53:00
● 2018-08-20 17:21:20
○ 2026-02-28 03:29:28
○ 2026-08-04 23:53:00
🔍 DNS Trace
Analysis
Name Servers
The NS records for sm021.com delegate to ns1.kouming.net and ns2.kouming.net.
sm021.com shares its NS records with other domains, for example xyxqb.com, 5kmk.com, fzzlmy.com and two others.
sm021.com and other domains like srkick.com share at least a portion of their name servers.
ns1.kouming.net resolves to 64.32.22.243 and 2610:150:c011:5:1::101. Likewise, ns2.kouming.net resolves to 103.97.0.246 and 2400:ede0:8000:1::5 — two IP addresses apiece.