`taguri-iot.com`

DNSSEC	⚠️ Not signed
A	168.76.72.102^{🇿🇦 ASLINE-AS-AP168.76.64.0/20 Proxy-registered route object}
NS	`n1.xundns.com` ⭐
		A	2409:8c44:1b00:601:1:1110:609:6027^{🇨🇳 CHINAMOBILE-CN2409:8c44:1b00::/48 CMI (Customer Route)}
		A	2604:86c0:5001:11::2659:466b^{🇺🇸 AS630232604:86c0:5000::/36 GTHOST-SEA}
		A	38.89.70.107^{🇺🇸 AS6302338.89.70.0/24 Route Registered for Cogent Communications Customer - GlobalTelehost Corp}
			PTR	`107-70-89-38.clients.gthost.com`
		A	103.236.52.145^{🇨🇳 CHINANET-Guangdong-ShenZhen-IDC103.236.52.0/22 Shenzhen Yunshangwuyou Communication Network Co., Ltd.-SZ IDC-Static multicast}
		A	111.6.96.27^{🇨🇳 CHINAMOBILE-CN111.6.96.0/21 CMI (Customer Route)}
NS	`n2.xundns.com`
		A	2408:8621:0:42:e401:813:0:25^{🇨🇳 CHINA169-Backbone2408:8621::/32 China Unicom B811&A1218, China Unicom No.21, Jin-Rong Street}
		A	2408:8722:1801:10:4:611:6303:181^{🇨🇳 CHINA169-Backbone2408:8722::/32 China Unicom B811&A1218, China Unicom No.21, Jin-Rong Street}
		A	2604:86c0:6001:8::a9c5:8e51^{🇺🇸 AS630232604:86c0:6000::/36 GTHOST-SCL}
		A	61.163.30.181^{🇨🇳 CHINA169-Backbone61.163.0.0/16 CNC Group CHINA169 Henan Province Network}
			PTR	`hn.ly.kd.adsl`
		A	122.114.39.7^{🇨🇳 CHINA169-Backbone122.114.0.0/16 route of Chinaunicomroute of Chinaunicom}
		A	169.197.142.81^{🇺🇸 AS63023169.197.142.0/24 GlobalTeleHost}
			PTR	`81-142-197-169.clients.gthost.com`
SOA	`n1.xundns.com`nsadmin@xundns.com serial=437896

`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.net`nstld@verisign-grs.com serial=1777125071

taguri-iot.com

7 records (3 active, 4 former)

○NSdns01.gmoserver.jp2017-05-12 → 2017-05-12 · 3 obs

● 2017-05-12 01:56:26
○ 2026-04-14 03:43:18
○ 2026-04-25 14:10:56

○NSdns02.gmoserver.jp2017-05-12 → 2017-05-12 · 3 obs

● 2017-05-12 01:56:26
○ 2026-04-14 03:43:18
○ 2026-04-25 14:10:56

●NSn1.xundns.com2026-04-14 → 2026-04-25 · 3 obs

○ 2017-05-12 01:56:26
● 2026-04-14 03:43:18
● 2026-04-25 14:10:56

●NSn2.xundns.com2026-04-14 → 2026-04-25 · 3 obs

○ 2017-05-12 01:56:26
● 2026-04-14 03:43:18
● 2026-04-25 14:10:56

○MXmx3.gmoserver.jp2017-05-12 → 2017-05-12 · 3 obs

● 2017-05-12 01:56:26
○ 2026-04-14 03:43:18
○ 2026-04-25 14:10:56

●A168.76.72.1022026-04-14 → 2026-04-25 · 3 obs

○ 2017-05-12 01:56:26
● 2026-04-14 03:43:18
● 2026-04-25 14:10:56

○A210.172.183.562017-05-12 → 2017-05-12 · 3 obs

● 2017-05-12 01:56:26
○ 2026-04-14 03:43:18
○ 2026-04-25 14:10:56

taguri-iot.com points to a single IP number: 168.76.72.102.

taguri-iot.com is delegated to two name servers: n1.xundns.com and n2.xundns.com.

taguri-iot.com uses the same name server setup as other domains, for instance lstysy.com, 53306.cn, ixuhang.com, 384455.com and 15625.cn.

taguri-iot.com shares name servers with other domains at least partially, for instance feedsafety.org, my-work.info, iloveyoutoronto.com, qqdgame.com and 21589c.com.

these name servers are commonly used together with v1s1.xundns.com and v1s2.xundns.com.