`servicesurabaya.com`

DNSSEC	⚠️ Not signed
A	103.131.51.174^{🇮🇩 IDNIC-JALANET-AS-ID103.131.51.0/24 Proxy-registered route object}
		PTR	`host.131.51.174.colo.co.id`
NS	`ns1.hoster.co.id` ⭐
		A	89.116.156.92^{🇺🇸 Limestone Networks89.116.156.0/24}
NS	`ns2.hoster.co.id`
		A	103.131.51.220^{🇮🇩 IDNIC-JALANET-AS-ID103.131.51.0/24 Proxy-registered route object}
			PTR	`host.131.51.220.colo.co.id`
NS	`ns3.hoster.co.id`
		A	89.116.44.81^{🇺🇸 Limestone Networks89.116.44.0/24}
NS	`ns4.hoster.co.id`
		A	103.131.51.196^{🇮🇩 IDNIC-JALANET-AS-ID103.131.51.0/24 Proxy-registered route object}
			PTR	`host.131.51.196.colo.co.id`
MX	`servicesurabaya.com` ⭐
		A	103.131.51.174^{🇮🇩 IDNIC-JALANET-AS-ID103.131.51.0/24 Proxy-registered route object}
			PTR	`host.131.51.174.colo.co.id`
TXT	`v=spf1 +a +mx +ip4:103.16.198.13 +ip4:103.131.51.46 +ip4:103.131.51.174 +ip4:...`
SOA	`ns1.hoster.co.id`bonechruser@hosterserver.com 2026-01-31 #1

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

MX for

servicesurabaya.com

Same first word

servicesurabaya.com

DNS History

18 records (6 active, 12 former)

○NSns.beonintermedia.com2015-05-06 → 2015-10-15 · 4 obs

● 2015-05-06 03:25:38
● 2015-10-15 18:40:52
○ 2015-12-31 05:41:08
○ 2026-03-28 10:02:38

○NSns.jagoanhosting.com2015-05-06 → 2015-10-15 · 4 obs

● 2015-05-06 03:25:38
● 2015-10-15 18:40:52
○ 2015-12-31 05:41:08
○ 2026-03-28 10:02:38

○NSns.jagoanweb.com2015-05-06 → 2015-10-15 · 4 obs

● 2015-05-06 03:25:38
● 2015-10-15 18:40:52
○ 2015-12-31 05:41:08
○ 2026-03-28 10:02:38

●NSns1.hoster.co.id2026-03-10 → 2026-03-28 · 3 obs

○ 2017-06-02 19:23:16
● 2026-03-10 15:47:14
● 2026-03-28 10:02:38

○NSns1.namebrightdns.com2017-06-02 → 2017-06-02 · 4 obs

○ 2016-11-25 10:17:44
● 2017-06-02 19:23:16
○ 2026-03-10 15:47:14
○ 2026-03-28 10:02:38

●NSns2.hoster.co.id2026-03-10 → 2026-03-28 · 3 obs

○ 2017-06-02 19:23:16
● 2026-03-10 15:47:14
● 2026-03-28 10:02:38

○NSns2.namebrightdns.com2017-06-02 → 2017-06-02 · 4 obs

○ 2016-11-25 10:17:44
● 2017-06-02 19:23:16
○ 2026-03-10 15:47:14
○ 2026-03-28 10:02:38

●NSns3.hoster.co.id2026-03-10 → 2026-03-28 · 3 obs

○ 2017-06-02 19:23:16
● 2026-03-10 15:47:14
● 2026-03-28 10:02:38

●NSns4.hoster.co.id2026-03-10 → 2026-03-28 · 3 obs

○ 2017-06-02 19:23:16
● 2026-03-10 15:47:14
● 2026-03-28 10:02:38

○NSns7.rookdns.com2016-04-04 → 2016-11-25 · 5 obs

○ 2015-12-31 05:41:08
● 2016-04-04 19:22:36
● 2016-11-25 10:17:44
○ 2017-06-02 19:23:16
○ 2026-03-28 10:02:38

○NSns8.rookdns.com2016-04-04 → 2016-11-25 · 5 obs

○ 2015-12-31 05:41:08
● 2016-04-04 19:22:36
● 2016-11-25 10:17:44
○ 2017-06-02 19:23:16
○ 2026-03-28 10:02:38

○MXmail.mxproc.com2016-04-04 → 2016-04-04 · 4 obs

○ 2015-12-31 05:41:08
● 2016-04-04 19:22:36
○ 2016-11-25 10:17:44
○ 2026-03-28 10:02:38

●MXservicesurabaya.com2015-05-06 → 2026-03-28 · 6 obs

● 2015-05-06 03:25:38
● 2015-10-15 18:40:52
○ 2015-12-31 05:41:08
○ 2017-06-02 19:23:16
● 2026-03-10 15:47:14
● 2026-03-28 10:02:38

○A101.50.1.322015-05-06 → 2015-10-15 · 4 obs

● 2015-05-06 03:25:38
● 2015-10-15 18:40:52
○ 2015-12-31 05:41:08
○ 2026-03-28 10:02:38

●A103.131.51.1742026-03-10 → 2026-03-28 · 3 obs

○ 2017-06-02 19:23:16
● 2026-03-10 15:47:14
● 2026-03-28 10:02:38

○A141.8.224.932016-04-04 → 2016-11-25 · 5 obs

○ 2015-12-31 05:41:08
● 2016-04-04 19:22:36
● 2016-11-25 10:17:44
○ 2017-06-02 19:23:16
○ 2026-03-28 10:02:38

○CNAMEhdredirect-lb3-890977680.us-east-1.elb.amazonaws.com2017-06-02 → 2017-06-02 · 3 obs

● 2017-06-02 19:23:16
○ 2026-03-10 15:47:14
○ 2026-03-28 10:02:38

○PTRns7.rookdns.com2016-11-25 → 2016-11-25 · 3 obs

● 2016-11-25 10:17:44
○ 2026-03-10 15:47:14
○ 2026-03-28 10:02:38

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	m.gtld-servers.net, b.gtld-servers.net, i.gtld-servers.net, h.gtld-servers.net...	-
servicesurabaya.com	ns1.hoster.co.id, ns2.hoster.co.id, ns3.hoster.co.id, ns4.hoster.co.id	-

✅ Authoritative Response

Server:103.131.51.196

NS records: ns1.hoster.co.id, ns2.hoster.co.id, ns3.hoster.co.id, ns4.hoster.co.id

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for servicesurabaya.com (unsigned zone)

⏱️ Timing

Total: 917ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`103.131.51.174`
NS	4	`ns1.hoster.co.id, ns3.hoster.co.id...`
MX	1	`servicesurabaya.com (pri: 0)`
TXT	1	`v=spf1 +a +mx +ip4:103.16.198.13 +ip4:10`
SOA	1	`ns1.hoster.co.id bonechruser.hosterserve`

Analysis

Mail Server Role

The mail server for servicesurabaya.com is servicesurabaya.com.

IP Addresses

servicesurabaya.com points to a single IP address: 103.131.51.174.

Other host names such as sbs.co.id, resonansi.co, mail.iof.or.id, iof.or.id and sampankalimantan.id share IPs with servicesurabaya.com.

Name Servers

servicesurabaya.com is delegated to four name servers: ns1.hoster.co.id, ns2.hoster.co.id, ns3.hoster.co.id and ns4.hoster.co.id.

servicesurabaya.com at least partially shares name servers with other domains, for example mitsubishicilegon.com, sahabatac.com, megasukses.com, istanamuara.com and pusatpromodaihatsu.com.

Host names with one IP number:

ns1.hoster.co.id points to: 89.116.156.92

ns2.hoster.co.id points to: 103.131.51.220

ns3.hoster.co.id points to: 89.116.44.81

ns4.hoster.co.id points to: 103.131.51.196

Mail Servers

One mail server handles servicesurabaya.com; that server is servicesurabaya.com.

servicesurabaya.com points to a single IP number: 103.131.51.174.

servicesurabaya.com - robtex.com