`lahoredispatch.com`

DNSSEC	⚠️ Not signed
A	154.222.136.208^{🇸🇨 USZNI-AS-AP154.222.136.0/23 zillion network}
NS	`dm1.longmingdns.com` ⭐
		A	218.98.111.163^{🇩🇪 HKCICL-AS-AP218.98.111.0/24 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED}
			PTR	`ip-218-98-111-163.defastlink.net`
NS	`dm2.longmingdns.com`
		A	183.253.57.197^{🇨🇳 CHINAMOBILE-CN183.253.0.0/16 CMI (Customer Route)}
			PTR	`ip-183-253-57-197.defastlink.net`
		A	211.99.99.56^{🇨🇳 DONGGUAN-1211.99.99.0/24 Proxy-registered route object}
			PTR	`ip-211-99-99-56.defastlink.net`
SOA	`dm1.longmingdns.com`dnsadmin@longmingdns.com serial=1770448098

`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=1771291435

Previously MX for

lahoredispatch.com

Same first word

lahoredispatch.com

DNS History

12 records (3 active, 9 former)

●NSdm1.longmingdns.com2026-02-25 → 2026-02-25 · 3 obs

○ 2019-12-29 04:05:34
● 2026-02-25 09:05:18
● 2026-02-25 13:02:20

●NSdm2.longmingdns.com2026-02-25 → 2026-02-25 · 3 obs

○ 2019-12-29 04:05:34
● 2026-02-25 09:05:18
● 2026-02-25 13:02:20

○NSdns1.websols.pk2015-08-05 → 2019-12-29 · 4 obs

● 2015-08-05 18:03:12
● 2019-12-29 04:05:34
○ 2026-02-25 09:05:18
○ 2026-02-25 13:02:20

○NSdns2.websols.pk2015-08-05 → 2019-12-29 · 4 obs

● 2015-08-05 18:03:12
● 2019-12-29 04:05:34
○ 2026-02-25 09:05:18
○ 2026-02-25 13:02:20

○MXlahoredispatch.com2019-12-29 → 2019-12-29 · 4 obs

○ 2017-03-15 10:12:52
● 2019-12-29 04:05:34
○ 2026-02-25 09:05:18
○ 2026-02-25 13:02:20

○MXmx001.servershost.net2015-08-05 → 2017-03-15 · 4 obs

● 2015-08-05 18:03:12
● 2017-03-15 10:12:52
○ 2019-12-29 04:05:34
○ 2026-02-25 13:02:20

○MXmx002.servershost.net2015-08-05 → 2017-03-15 · 4 obs

● 2015-08-05 18:03:12
● 2017-03-15 10:12:52
○ 2019-12-29 04:05:34
○ 2026-02-25 13:02:20

●A154.222.136.2082026-02-25 → 2026-02-25 · 3 obs

○ 2019-12-29 04:05:34
● 2026-02-25 09:05:18
● 2026-02-25 13:02:20

○A158.69.241.1162016-07-09 → 2019-12-29 · 5 obs

○ 2016-03-03 21:25:44
● 2016-07-09 23:37:54
● 2019-12-29 04:05:34
○ 2026-02-25 09:05:18
○ 2026-02-25 13:02:20

○A167.114.209.762016-03-03 → 2016-03-03 · 4 obs

○ 2015-11-23 13:47:36
● 2016-03-03 21:25:44
○ 2016-07-09 23:37:54
○ 2026-02-25 13:02:20

○A192.99.13.2062015-08-05 → 2015-08-05 · 3 obs

● 2015-08-05 18:03:12
○ 2015-11-23 13:47:36
○ 2026-02-25 13:02:20

○A198.23.192.1222015-11-23 → 2015-11-23 · 4 obs

○ 2015-08-05 18:03:12
● 2015-11-23 13:47:36
○ 2016-03-03 21:25:44
○ 2026-02-25 13:02:20

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	e.gtld-servers.net, l.gtld-servers.net, i.gtld-servers.net, h.gtld-servers.net...	-
lahoredispatch.com	dm2.longmingdns.com, dm1.longmingdns.com	5 records

✅ Authoritative Response

Server: 218.98.111.163

NS records: dm2.longmingdns.com, dm1.longmingdns.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for lahoredispatch.com (unsigned zone)

⏱️ Timing

Total: 3641ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`154.222.136.208`
NS	2	`dm1.longmingdns.com, dm2.longmingdns.com`
SOA	1	`dm1.longmingdns.com dnsadmin.longmingdns`

📌 Glue Records Collected

Total: 5

Out-of-bailiwick: 5 (dm2.longmingdns.com, dm2.longmingdns.com, dm2.longmingdns.com...)

AI analysis

lahoredispatch.com points to IP number: 154.222.136.208.

lahoredispatch.com is delegated to two name servers: dm1.longmingdns.com and dm2.longmingdns.com.

lahoredispatch.com shares the same name server setup as fensijie.cn, whjlcq.cn, 21dnf.cn, pqkn.cn and 888099.cn.

Host names with two IP numbers:

dm2.longmingdns.com points to 183.253.57.197 and 211.99.99.56.

Host names with one IP number:

dm1.longmingdns.com points to 218.98.111.163.

lahoredispatch.com - robtex.com