DNSWHOIS.INFO - loops.id

Search for IP or hostnames:

loops.id checked at 2025-09-06T05:49:48.601Z 336ms 143/143/143 100% R:13

`loops.id`

NS	`ns1.digitalocean.com`
		A	2606:4700:52::ac40:34d2 ^{🇺🇸 Cloudflare}
			PTR	`ns1.digitalocean.com`
		A	172.64.52.210^{🇺🇸 Cloudflare}
			PTR	`ns1.digitalocean.com`
NS	`ns2.digitalocean.com`
		A	2606:4700:5a::ac40:3515 ^{🇺🇸 Cloudflare}
			PTR	`ns2.digitalocean.com`
		A	172.64.53.21^{🇺🇸 Cloudflare}
			PTR	`ns2.digitalocean.com`
NS	`ns3.digitalocean.com`
		A	2606:4700:52::ac40:31d1 ^{🇺🇸 Cloudflare}
			PTR	`ns3.digitalocean.com`
		A	172.64.49.209^{🇺🇸 Cloudflare}
			PTR	`ns3.digitalocean.com`
MX	`inbound-smtp.us-west-2.amazonaws.com`
		A	35.161.157.106^{🇺🇸 Amazon}
			PTR	`ec2-35-161-157-106.us-west-2.compute.amazonaws.com`
		A	52.13.163.116^{🇺🇸 Amazon}
			PTR	`ec2-52-13-163-116.us-west-2.compute.amazonaws.com`
		A	52.43.162.244^{🇺🇸 Amazon}
			PTR	`ec2-52-43-162-244.us-west-2.compute.amazonaws.com`
		A	54.188.121.70^{🇺🇸 Amazon}
			PTR	`ec2-54-188-121-70.us-west-2.compute.amazonaws.com`
MX	`aspmx.l.google.com`
		A	2607:f8b0:4004:c0b::1a ^{🇺🇸 Google}
			PTR	`bj-in-f26.1e100.net`
		A	142.251.16.27^{🇺🇸 Google}
			PTR	`bl-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`
		A	2a00:1450:400b:c02::1a ^{🇮🇪 Google}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.26^{🇺🇸 Google}
			PTR	`dj-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`
		A	2a00:1450:400c:c00::1b ^{🇧🇪 Google}
			PTR	`ws-in-f27.1e100.net`
			PTR	`ws-in-x1b.1e100.net`
		A	173.194.76.27^{🇺🇸 Google}
			PTR	`ws-in-f27.1e100.net`
MX	`alt3.aspmx.l.google.com`
		A	2a00:1450:4025:402::1b ^{🇳🇱 Google}
			PTR	`rb-in-f27.1e100.net`
		A	142.250.102.27^{🇺🇸 Google}
			PTR	`rb-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`
		A	2a00:1450:4013:c1c::1b ^{🇳🇱 Google}
			PTR	`yugrqog-in-f27.1e100.net`
		A	192.178.156.27^{🇺🇸 Google}
			PTR	`yugrqog-in-f27.1e100.net`
A	152.42.161.44^{🇺🇸 DigitalOcean}

`id`

	NS	`b.dns.id`
	NS	`c.dns.id`
	NS	`d.dns.id`
	NS	`e.dns.id`
	NS	`ns4.apnic.net`

Up
`app.loops.id`

Starts with same word
`loops.us`
`loops.es`
`loops.org`
`loops.io`
`loops.at`
`loops.tv`
`loops.se`
`loops.cl`
`loops.studio`
`loops.jp`
`loops.gr`
`loops.it`
`loops.nl`
`loops.com`
`loops.fm`
`loops.cc`
`loops.net`
`loops.co`
`loops.ru`
`loops.lk`
`loops.no`
`loops.education`
`loops.fun`
`loops.pk`
`loops.id`
`loops.cat`
`loops.my`
`loops.de`
`loops.kz`
`loops.cn`
`loops.ch`

Starts similarily
`pools.eu`
`polos.cz`
`plsoo.org`
`pools.ru`
`spool.us`
`loops.id`
`polos.ch`
`solpo.eu`
`loops.cat`
`pools.solar`
`pools.es`
`sloop.biz`
`sloop.ca`
`loops.my`
`soplo.ru`
`polos.co.in`
`psolo.com`
`sloop.eu`
`spool.eu`
`pools.su`
`loops.de`
`pools.jp`
`loops.kz`
`polos.net`
`sloop.net`
`loops.cn`
`pools.uz`
`loops.ch`
`pools.us`
`spool.fm`
`sloop.us`
`loops.us`
`loops.es`
`soopl.fr`
`spolo.cn`
`pools.sg`
`polos.be`
`polos.se`
`spool.es`
`spool.tv`
`sloop.in`
`pools.cool`
`sloop.me`
`spool.uk.com`
`polos.eu`
`loops.org`
`opsol.us`
`polos.es`
`soopl.nl`
`losop.com`
`polos.gov.mz`
`pools.ae`
`ploos.ru`
`pools.ws`
`spolo.net`
`opsol.de`
`polos.ru`
`soopl.es`
`loops.io`
`polos.org`
`pools.biz`
`loops.at`
`sloop.co.uk`
`posol.de`
`posol.ru`
`spool.cz`
`loops.tv`
`loops.se`
`ploos.org`
`sloop.de`
`polos.sp.gov.br`
`soopl.it`
`pools.kz`
`soolp.com`
`pools.ch`
`sloop.ch`
`spool.se`
`loops.cl`
`spool.lv`
`pools.mx`
`polos.cn`
`polos.fr`
`pools.be`
`sopol.pl`
`polos.ae`
`ploos.nl`
`pools.tv`
`spool.ru`
`sloop.info`
`opsol.net`
`pools.com.ua`
`opsol.com.au`
`posol.cn`
`spolo.de`
`pools.gr`
`soopl.co.uk`
`spool.dk`
`pools.no`
`spool.jp`
`spool.org`

AI analysis

The parent of app.loops.id is loops.id.

loops.id is configured to point to the IP address 152.42.161.44.

Three name servers, ns1.digitalocean.com, ns2.digitalocean.com, and ns3.digitalocean.com, are delegated to loops.id.

The domain loops.id shares name servers, at least in part, with other domains such as marketiva.com, auxopolis.com, patientaid.net, preparati-potencija.com, and drazenj.com.

ns1.digitalocean.com, 2606:4700:52::ac40:34d2, and 172.64.52.210 are connected via DNS.

ns2.digitalocean.com, 2606:4700:5a::ac40:3515, and 172.64.53.21 are linked through DNS.

ns3.digitalocean.com, 2606:4700:52::ac40:31d1, and 172.64.49.209 are associated through DNS.

The handling of loops.id is managed by six mail servers, namely inbound-smtp.us-west-2.amazonaws.com, aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com, and alt4.aspmx.l.google.com.

Some mail servers of loops.id are partially shared with other domains such as igordon.org, ghsimr.ac.in, usenewton.com, workathome.net, and crescentqualitymeats.com.

The mail servers inbound-smtp.us-east-1.amazonaws.com, aspmx2.googlemail.com, and aspmx3.googlemail.com are frequently utilized in conjunction with these mail servers.

inbound-smtp.us-west-2.amazonaws.com points to four IP numbers: 35.161.157.106, 52.13.163.116, 52.43.162.244, and 54.188.121.70. aspmx.l.google.com points to two IP numbers: 2607:f8b0:4004:c0b::1a and 142.251.16.27. alt1.aspmx.l.google.com points to two IP numbers: 2a00:1450:400b:c02::1a and 172.253.116.26. alt2.aspmx.l.google.com points to two IP numbers: 2a00:1450:400c:c00::1b and 173.194.76.27. alt3.aspmx.l.google.com points to two IP numbers: 2a00:1450:4025:402::1b and 142.250.102.27. alt4.aspmx.l.google.com points to two IP numbers: 2a00:1450:4013:c1c::1b and 192.178.156.27.

dbq