CF1757311370410-tsm20250907181809

NSLIST.NET - didna.io

Search for IP or hostnames:

didna.io checked at 2025-09-08T06:02:50.394Z 395ms 141/141/141 100% R:18

`didna.io`

	NS	`ns-242.awsdns-30.com`
			A	2600:9000:5300:f200::1 ^{🇺🇸 Amazon}
				PTR	`ns-242.awsdns-30.com`
			A	205.251.192.242^{🇺🇸 Amazon}
				PTR	`ns-242.awsdns-30.com`
	NS	`ns-610.awsdns-12.net`
			A	2600:9000:5302:6200::1 ^{🇺🇸 Amazon}
				PTR	`ns-610.awsdns-12.net`
			A	205.251.194.98^{🇺🇸 Amazon}
				PTR	`ns-610.awsdns-12.net`
	NS	`ns-1122.awsdns-12.org`
			A	2600:9000:5304:6200::1 ^{🇺🇸 Amazon}
				PTR	`ns-1122.awsdns-12.org`
			A	205.251.196.98^{🇺🇸 Amazon}
				PTR	`ns-1122.awsdns-12.org`
	MX	`aspmx.l.google.com`
			A	2607:f8b0:4004:c0b::1b ^{🇺🇸 Google}
				PTR	`bj-in-f27.1e100.net`
			A	142.251.163.26^{🇺🇸 Google}
				PTR	`wv-in-f26.1e100.net`
	NS	`ns-1897.awsdns-45.co.uk`
			A	2600:9000:5307:6900::1 ^{🇺🇸 Amazon}
				PTR	`ns-1897.awsdns-45.co.uk`
			A	205.251.199.105^{🇺🇸 Amazon}
				PTR	`ns-1897.awsdns-45.co.uk`
	MX	`alt1.aspmx.l.google.com`
			A	2a00:1450:400b:c02::1b ^{🇮🇪 Google}
				PTR	`dj-in-f27.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.26^{🇺🇸 Google}
				PTR	`ws-in-f26.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::1a ^{🇳🇱 Google}
				PTR	`yugrqog-in-f26.1e100.net`
			A	192.178.156.27^{🇺🇸 Google}
				PTR	`yugrqog-in-f27.1e100.net`
	A	157.230.213.145^{🇺🇸 DigitalOcean}
			PTR	`didna.io`

`io`

	NS	`a0.nic.io`
	NS	`a2.nic.io`
	NS	`b0.nic.io`
	NS	`c0.nic.io`

PTR for
`145.213.230.157.in-addr.arpa`

Up
`servs.didna.io`
`serv.didna.io`
`site.didna.io`

Starts with same word
`didna.ir`
`didna.com`
`didna.io`

Starts similarily
`addin.icu`
`ddian.net`
`ddina.com`
`dandi.cat`
`ddian.com`
`dandi.dk`
`addin.ch`
`adnid.eu`
`didan.ru`
`didan.es`
`didan.org`
`diand.cn`
`addin.es`
`addin.xyz`
`dandi.se`
`dandi.co.uk`
`nadid.net`
`adnid.info`
`adnid.org`
`dandi.ru`
`dndai.cn`
`didan.ir`
`dadin.com.tw`
`didna.com`
`dinda.com`
`addin.ca`
`diand.ro`
`addin.dk`
`dandi.it`
`ddani.info`
`addin.pt`
`nadid.com`
`addin.meet`
`dinda.de`
`danid.dk`
`dinad.net`
`andid.com`
`dinad.org.ar`
`ddian.cn`
`indad.com.ar`
`didan.de`
`aiddn.co.jp`
`dandi.com`
`addin.pro`
`nidad.com`
`anddi.pt`
`didan.biz`
`dandi.cn`
`iddan.com`
`iddan.github.io`
`addin.org`
`ddani.github.io`
`dinda.nl`
`addin.in`
`anidd.space`
`iddna.net`
`ddnai.com`
`addin.biz`
`nidda.de`
`nidda.org`
`dandi.in`
`iandd.com`
`diand.tempurl.host`
`indad.co.kr`
`diand.info`
`dandi.ca`
`dinda.org`
`nidda.info`
`dinda.eu`
`ndida.com`
`adnid.com`
`addin.kr`
`addin.us`
`dadin.de`
`indad.com`
`dandi.me`
`danid.com`
`addin.eu`
`didna.io`
`danid.ch`
`niadd.com`
`ddani.com`
`addin.co.th`
`diand.ca`
`dandi.us`
`dinda.info`
`naddi.org`
`adndi.com`
`nidda.com`
`adind.com`
`dndai.com`
`dadin.eu`
`dandi.org`
`addin.cc`
`didan.eu`
`dandi.si`
`addin.it`
`dinda.it`
`danid.org`
`dinda.net`
`dandi.eu`
`dandi.ro`
`addni.net`
`didan.com`
`ndadi.com`
`dandi.work`
`didna.ir`
`dandi.de`
`addin.de`
`dinda.name`
`addin.ru`
`dandi.com.br`
`dandi.com.cn`
`addin.se`
`dandi.media`
`danid.net`
`dandi.com.ng`
`andid.cn`
`nidda.eu`

AI analysis

The parent of servs.didna.io, serv.didna.io, and site.didna.io is didna.io.

didna.io is associated with a single IP address: 157.230.213.145.

For example, other host names such as site.didna.io share IP numbers with didna.io.

Four name servers, ns-242.awsdns-30.com, ns-610.awsdns-12.net, ns-1122.awsdns-12.org, and ns-1897.awsdns-45.co.uk, are assigned to didna.io.

The domain didna.io shares name servers, at least partially, with other domains such as d2zoruoj1168bv.cloudfront.net, philipwhitt.com, lpesecurity.com, travelforest.co.kr, and 139.107.192.in-addr.arpa.

The name servers ns-1394.awsdns-46.org, ns-194.awsdns-24.com, ns-1986.awsdns-56.co.uk, ns-826.awsdns-39.net, ns-1909.awsdns-46.co.uk, ns-219.awsdns-27.com, ns-320.awsdns-40.com, ns-435.awsdns-54.com, ns-579.awsdns-08.net, and ns-239.awsdns-29.com are frequently utilized in conjunction.

ns-242.awsdns-30.com, ns-610.awsdns-12.net, ns-1122.awsdns-12.org, and ns-1897.awsdns-45.co.uk all point to two IP numbers each: 2600:9000:5300:f200::1 and 205.251.192.242, 2600:9000:5302:6200::1 and 205.251.194.98, 2600:9000:5304:6200::1 and 205.251.196.98, 2600:9000:5307:6900::1 and 205.251.199.105 respectively.

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 didna.io.

Some mail servers are at least partially shared between didna.io and other domains, such as verisign.io, correo.unicordoba.edu.co, perl.kr, connecti-on.com, and abetena.com.

The mail servers aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com, aspmx5.googlemail.com, and nj2ltef7cfnpdu2ct3pcvw3didw5t5rggyp7cvjbl6ddm6epqhea.mx-verification.google.com are typically used concurrently.

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 all point to two IP numbers each: 2607:f8b0:4004:c0b::1b and 142.251.163.26, 2a00:1450:400b:c02::1b and 172.253.116.26, 2a00:1450:400c:c00::1b and 173.194.76.26, 2a00:1450:4025:402::1a and 142.250.102.26, 2a00:1450:4013:c1c::1a and 192.178.156.27 respectively.

dbq

nAqiMgf CF johedugfp 2025-09-08