NSLIST.NET - signal.design

Search for IP or hostnames:

signal.design checked at 2025-09-10T03:38:08.437Z 269ms 120/120/120 100% R:13

`signal.design`

NS	`ns75.domaincontrol.com`
		A	2603:5:21b4::30 ^{🇺🇸 GODADDY-DNS}
			PTR	`ns75.domaincontrol.com`
		A	97.74.107.48^{🇺🇸 GODADDY-DNS}
			PTR	`ns75.domaincontrol.com`
NS	`ns76.domaincontrol.com`
		A	2603:5:22b4::30 ^{🇺🇸 GODADDY-DNS}
			PTR	`ns76.domaincontrol.com`
		A	173.201.75.48^{🇺🇸 GODADDY-DNS}
			PTR	`ns76.domaincontrol.com`
MX	`aspmx.l.google.com`
		A	2607:f8b0:4004:c07::1b ^{🇺🇸 Google}
			PTR	`bc-in-f27.1e100.net`
		A	172.253.122.27^{🇺🇸 Google}
			PTR	`bh-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::1a ^{🇳🇱 Google}
			PTR	`rb-in-f26.1e100.net`
		A	142.250.102.26^{🇺🇸 Google}
			PTR	`rb-in-f26.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	3.33.130.190^{🇺🇸 Amazon}
		PTR	`a2aa9ff50de748dbe.awsglobalaccelerator.com`
A	15.197.148.33^{🇺🇸 Amazon}
		PTR	`a2aa9ff50de748dbe.awsglobalaccelerator.com`

`design`

	NS	`a.nic.design`
	NS	`b.nic.design`
	NS	`c.nic.design`
	NS	`x.nic.design`
	NS	`y.nic.design`
	NS	`z.nic.design`

Starts with same word
`signal.institute`
`signal.eu.org`
`signal.be`
`signal.com.pe`
`signal.network`
`signal.sh`
`signal.studio`
`signal.biz`
`signal.tax`
`signal.tv`
`signal.es`
`signal.bz`
`signal.bg`
`signal.events`
`signal.me`
`signal.fr`
`signal.ws`
`signal.ltd`
`signal.hu`
`signal.ca`
`signal.jp`
`signal.sa`
`signal.co.jp`
`signal.ventures`
`signal.sk`
`signal.cafe`
`signal.az`
`signal.email`
`signal.lk`
`signal.ec`
`signal.ru`
`signal.ninja`
`signal.watch`
`signal.group`
`signal.com.tr`
`signal.com.br`
`signal.org`
`signal.com`
`signal.tips`
`signal.ly`
`signal.net.ua`
`signal.uk.com`
`signal.expert`
`signal.ch`
`signal.vinnica.ua`
`signal.art`
`signal.fm`
`signal.nl`
`signal.plus`
`signal.at`
`signal.ir`
`signal.id`
`signal.live`
`signal.digital`
`signal.com.ua`
`signal.codes`
`signal.no`
`signal.org.uk`
`signal.beer`
`signal.cl`
`signal.is`
`signal.ovh`
`signal.life`
`signal.tokyo`
`signal.report`
`signal.agency`
`signal.cool`
`signal.academy`
`signal.co`
`signal.club`
`signal.design`
`signal.blue`
`signal.co.ir`
`signal.de`
`signal.my.id`
`signal.pl`
`signal.co.id`
`signal.center`
`signal.dk`

Starts similarily
`silgan.com`
`signal.uk.com`
`inglas.nl`
`signal.expert`
`ingals.com`
`singla.me`
`signal.ch`
`signal.vinnica.ua`
`asling.com`
`naglis.us`
`signal.art`
`signal.fm`
`gsnail.com`
`gsnail.net`
`signal.nl`
`signal.plus`
`siglan.com`
`slaing.net`
`signal.at`
`signal.ir`
`signal.id`
`signal.live`
`singla.net`
`signal.digital`
`ignals.com`
`signal.com.ua`
`signal.codes`
`sangil.mx`
`signal.no`
`signal.org.uk`
`signal.beer`
`signal.cl`
`signal.is`
`lingas.com`
`inglas.eu`
`signal.ovh`
`inglas.dk`
`sangil.gov.co`
`sailng.com`
`laings.com.au`
`lisang.ca`
`glisan.com`
`lingsa.org`
`singla.in`
`laings.co.uk`
`singla.ru`
`signal.life`
`signal.tokyo`
`saling.org`
`sangli.in`
`signal.report`
`signal.agency`
`signal.cool`
`inglas.de`
`sangil.es`
`siganl.de`
`signal.academy`
`gnails.com`
`niglas.ac.cn`
`sinagl.cz`
`signal.co`
`signal.club`
`alsign.org`
`laings.com`
`slaing.com`
`langis.ch`
`silang.gov.ph`
`gaslin.ddns.net`
`silgan.net`
`signal.design`
`saling.io`
`signal.blue`
`naglis.lt`
`singal.net`
`saling.gmbh`
`alsing.org`
`signal.co.ir`
`saling.net`
`saling.biz`
`gnails.se`
`signal.de`
`sangil.net`
`alsing.no`
`saling.com`
`sangli.nic.in`
`sangli.gov.in`
`signal.my.id`
`naglis.nyc`
`salgin.de`
`sangli.co.in`
`singla.org`
`signal.pl`
`signal.co.id`
`slangi.net`
`asling.com.au`
`signal.center`
`signal.dk`
`singal.org`
`singal.or.kr`
`glasin.se`
`laings.org.uk`
`langis.ca`
`signal.institute`
`signal.eu.org`
`signal.be`
`laings.net`
`asling.org`
`signal.com.pe`
`signal.network`
`langis.com`
`laings.us`
`signal.sh`
`saling.ch`
`naglis.com`
`anglis.com`
`sinlag.com`
`saling.co`
`ilsang.biz`
`signal.studio`
`gnails.be`
`singla.co`
`lasing.com`
`signal.biz`
`sangil.de`
`signal.tax`
`signal.tv`
`lingas.sk`
`silang.com.cn`
`signal.es`
`lasign.com`
`glasin.com`
`inglas.com`
`langis.net`
`signal.bz`
`signal.bg`
`alsing.net`
`signal.events`
`glanis.ch`
`signal.me`
`lasgin.com`
`signal.fr`
`glinas.se`
`sangli.com`
`saglin.net`
`silang.org`
`signal.ws`
`saling.at`
`asling.se`
`signal.ltd`
`lisang.com`
`silgan.de`
`signal.hu`
`signal.ca`
`signla.com`
`signal.jp`
`signal.sa`
`saling.info`
`signal.co.jp`
`inglas.pl`
`sangil.com.co`
`glasin.nl`

AI analysis

signal.design points to two IP numbers: 3.33.130.190 and 15.197.148.33.

IP numbers are shared between signal.design and other host names such as eldify.com, hampham.com, mediapr.org, kastians.com, and gabriellajoyce.com.

Two name servers, ns75.domaincontrol.com and ns76.domaincontrol.com, are delegated to signal.design.

The name server setup of signal.design is shared with other domains such as mrsfl.org, mvresellers.com, nationalinfantryfoundation.com, holisti.co, and scopecozy.com.

ns75.domaincontrol.com and ns76.domaincontrol.com each point to two IP numbers. For ns75.domaincontrol.com, these are 2603:5:21b4::30 and 97.74.107.48, while for ns76.domaincontrol.com, they are 2603:5:22b4::30 and 173.201.75.48.

The five mail servers, 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, are responsible for handling signal.design.

Other domains such as omnikinetics.com, caleblam.com, roulot.pro, sbntech.com, and goldfinllc.com share at least some mail servers with signal.design.

The mail servers aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com, and aspmx5.googlemail.com are commonly used in conjunction with these mail servers.

aspmx.l.google.com, 2607:f8b0:4004:c07::1b, and 172.253.122.27 are associated with each other.

alt1.aspmx.l.google.com, 2a00:1450:400b:c02::1a, and 172.253.116.26 are interconnected.

alt2.aspmx.l.google.com, 2a00:1450:400c:c00::1b, and 173.194.76.27 are linked together.

alt3.aspmx.l.google.com, 2a00:1450:4025:402::1a, and 142.250.102.26 are correlated.

alt4.aspmx.l.google.com, 2a00:1450:4013:c1c::1b, and 192.178.156.27 are related to each other.

dbq