icms.pk - robtex.com

icms.pk

DNSSECโš ๏ธ Not signed
A38.180.225.218๐Ÿ‡ณ๐Ÿ‡ฑ M-138.180.225.0/24 As an internet service provider (ISP), we offer IP transit and bandwidth services that are self-managed by our customers. As a result, we do not utilize this IP space ourselves. If you encounter any issues related to spam, fraud, phishing, DDoS, port scans, or other similar problems, please do not hesitate to reach out to us with the relevant information. Our abuse email is abuse@3nt.com
NSns1.regery.net โญ
A136.243.218.113๐Ÿ‡ฉ๐Ÿ‡ช Hetzner136.243.0.0/16 HETZNER-RZ-BLK-ERX3
PTRstatic.113.218.243.136.clients.your-server.de
NSns2.regery.net
A136.243.218.114๐Ÿ‡ฉ๐Ÿ‡ช Hetzner136.243.0.0/16 HETZNER-RZ-BLK-ERX3
PTRstatic.114.218.243.136.clients.your-server.de
NSns3.regery.net
A116.202.42.237๐Ÿ‡ฉ๐Ÿ‡ช Hetzner116.202.0.0/16 HETZNER-DC
PTRstatic.237.42.202.116.clients.your-server.de
SOAns1.regery.netsupport@regery.com 2025-08-21 #79

pk

DNSSECโš ๏ธ Not signed
NSpknic.pk โญ
NSroot-c1.pknic.pk
NSroot-c2.pknic.pk
NSroot-e.pknic.pk
NSroot-s.pknic.pk
SOApknic.pkstaf(0x664070)knic.net.pk 2026-06-19 #88

Same first word

Similar names

DNS History

17 records (4 active, 13 former)

20162017201820192020202120222023202420252026NSns1.regery.netns2.regery.netns3.regery.netn1.hostnext.netn2.hostnext.netns5.hostnext.netns6.hostnext.netMXalt1.aspmx.l.google.comalt2.aspmx.l.google.comalt3.aspmx.l.google.comalt4.aspmx.l.google.comaspmx.l.google.comA38.180.225.218131.153.38.171198.15.104.12650.87.55.2250.97.79.227
โ—‹NSn1.hostnext.net2016-03-17 โ†’ 2017-09-27 ยท 5 obs
โ—‹ 2015-12-13 02:52:22
โ— 2016-03-17 05:18:58
โ— 2017-09-27 12:54:18
โ—‹ 2026-06-10 01:35:42
โ—‹ 2026-06-19 19:14:32
โ—‹NSn2.hostnext.net2016-03-17 โ†’ 2017-09-27 ยท 5 obs
โ—‹ 2015-12-13 02:52:22
โ— 2016-03-17 05:18:58
โ— 2017-09-27 12:54:18
โ—‹ 2026-06-10 01:35:42
โ—‹ 2026-06-19 19:14:32
โ—NSns1.regery.net2026-06-10 โ†’ 2026-06-19 ยท 3 obs
โ—‹ 2017-09-27 12:54:18
โ— 2026-06-10 01:35:42
โ— 2026-06-19 19:14:32
โ—NSns2.regery.net2026-06-10 โ†’ 2026-06-19 ยท 3 obs
โ—‹ 2017-09-27 12:54:18
โ— 2026-06-10 01:35:42
โ— 2026-06-19 19:14:32
โ—NSns3.regery.net2026-06-10 โ†’ 2026-06-19 ยท 3 obs
โ—‹ 2017-09-27 12:54:18
โ— 2026-06-10 01:35:42
โ— 2026-06-19 19:14:32
โ—‹NSns5.hostnext.net2015-08-01 โ†’ 2015-12-13 ยท 4 obs
โ— 2015-08-01 08:19:00
โ— 2015-12-13 02:52:22
โ—‹ 2016-03-17 05:18:58
โ—‹ 2026-06-19 19:14:32
โ—‹NSns6.hostnext.net2015-08-01 โ†’ 2015-12-13 ยท 4 obs
โ— 2015-08-01 08:19:00
โ— 2015-12-13 02:52:22
โ—‹ 2016-03-17 05:18:58
โ—‹ 2026-06-19 19:14:32
โ—‹MXalt1.aspmx.l.google.com2015-08-01 โ†’ 2017-09-27 ยท 4 obs
โ— 2015-08-01 08:19:00
โ— 2017-09-27 12:54:18
โ—‹ 2026-06-10 01:35:42
โ—‹ 2026-06-19 19:14:32
โ—‹MXalt2.aspmx.l.google.com2015-08-01 โ†’ 2017-09-27 ยท 4 obs
โ— 2015-08-01 08:19:00
โ— 2017-09-27 12:54:18
โ—‹ 2026-06-10 01:35:42
โ—‹ 2026-06-19 19:14:32
โ—‹MXalt3.aspmx.l.google.com2015-08-01 โ†’ 2017-09-27 ยท 4 obs
โ— 2015-08-01 08:19:00
โ— 2017-09-27 12:54:18
โ—‹ 2026-06-10 01:35:42
โ—‹ 2026-06-19 19:14:32
โ—‹MXalt4.aspmx.l.google.com2015-08-01 โ†’ 2017-09-27 ยท 4 obs
โ— 2015-08-01 08:19:00
โ— 2017-09-27 12:54:18
โ—‹ 2026-06-10 01:35:42
โ—‹ 2026-06-19 19:14:32
โ—‹MXaspmx.l.google.com2015-08-01 โ†’ 2017-09-27 ยท 4 obs
โ— 2015-08-01 08:19:00
โ— 2017-09-27 12:54:18
โ—‹ 2026-06-10 01:35:42
โ—‹ 2026-06-19 19:14:32
โ—‹A131.153.38.1712016-12-19 โ†’ 2017-09-27 ยท 5 obs
โ—‹ 2016-04-24 10:03:20
โ— 2016-12-19 10:19:10
โ— 2017-09-27 12:54:18
โ—‹ 2026-06-10 01:35:42
โ—‹ 2026-06-19 19:14:32
โ—‹A198.15.104.1262016-03-17 โ†’ 2016-04-24 ยท 5 obs
โ—‹ 2015-12-13 02:52:22
โ— 2016-03-17 05:18:58
โ— 2016-04-24 10:03:20
โ—‹ 2016-12-19 10:19:10
โ—‹ 2026-06-19 19:14:32
โ—A38.180.225.2182026-06-10 โ†’ 2026-06-19 ยท 3 obs
โ—‹ 2017-09-27 12:54:18
โ— 2026-06-10 01:35:42
โ— 2026-06-19 19:14:32
โ—‹A50.87.55.222015-09-15 โ†’ 2015-12-13 ยท 5 obs
โ—‹ 2015-08-01 08:19:00
โ— 2015-09-15 04:37:22
โ— 2015-12-13 02:52:22
โ—‹ 2016-03-17 05:18:58
โ—‹ 2026-06-19 19:14:32
โ—‹A50.97.79.2272015-08-01 โ†’ 2015-08-01 ยท 3 obs
โ— 2015-08-01 08:19:00
โ—‹ 2015-09-15 04:37:22
โ—‹ 2026-06-19 19:14:32

๐Ÿ” DNS Trace

๐Ÿ“‹ Delegation Chain

ZoneNameserversGlue
pkroot-c2.pknic.pk, root-s.pknic.pk, root-e.pknic.pk, root-c1.pknic.pk6 records
icms.pkns2.regery.net, ns3.regery.net, ns1.regery.net-

โœ… Authoritative Response

Server:136.243.218.114

NS records: ns2.regery.net, ns3.regery.net, ns1.regery.net

๐Ÿ”’ DNSSEC Status

โš ๏ธ Insecure (no DNSSEC)

No DS record for pk (unsigned zone)

โฑ๏ธ Timing

Total: 3499ms | Queries: -

๐Ÿ“„ Records

TypeCountSample Data
A138.180.225.218
NS3ns3.regery.net, ns1.regery.net...
SOA1ns1.regery.net support.regery.com

๐Ÿ“Œ Glue Records Collected

Total: 6

In-bailiwick: 6 (root-c2.pknic.pk, root-c2.pknic.pk, root-s.pknic.pk...)

Analysis

IP Addresses

icms.pk points to a single IP number: 38.180.225.218.

aromausb.com, for instance, is one of the other host names sharing IP numbers with icms.pk.

Name Servers

The authoritative name servers for icms.pk are ns1.regery.net, ns2.regery.net and ns3.regery.net โ€” three in total.

icms.pk shares at least some of its name servers with other domains, including alsafeersport.com, ios-data-recover.com, topfoto.net and two others.

The hostnames ns1.regery.net, ns2.regery.net and ns3.regery.net each resolve to a single IP: ns1.regery.net โ†’ 136.243.218.113, ns2.regery.net โ†’ 136.243.218.114, ns3.regery.net โ†’ 116.202.42.237.