WWW.RTSAK.COM - nostr.build

Search for IP or hostnames:

nostr.build checked at 2025-09-06T21:10:04.483Z 302ms 171/171/171 100% R:12

`nostr.build`

NS	`ns-411.awsdns-51.com`
		A	2600:9000:5301:9b00::1 ^{🇺🇸 Amazon}
			PTR	`ns-411.awsdns-51.com`
		A	205.251.193.155^{🇺🇸 Amazon}
			PTR	`ns-411.awsdns-51.com`
NS	`ns-749.awsdns-29.net`
		A	2600:9000:5302:ed00::1 ^{🇺🇸 Amazon}
			PTR	`ns-749.awsdns-29.net`
		A	205.251.194.237^{🇺🇸 Amazon}
			PTR	`ns-749.awsdns-29.net`
NS	`ns-1326.awsdns-37.org`
		A	2600:9000:5305:2e00::1 ^{🇺🇸 Amazon}
			PTR	`ns-1326.awsdns-37.org`
		A	205.251.197.46^{🇺🇸 Amazon}
			PTR	`ns-1326.awsdns-37.org`
NS	`ns-1933.awsdns-49.co.uk`
		A	2600:9000:5307:8d00::1 ^{🇺🇸 Amazon}
			PTR	`ns-1933.awsdns-49.co.uk`
		A	205.251.199.141^{🇺🇸 Amazon}
			PTR	`ns-1933.awsdns-49.co.uk`
MX	`nostr-build.mail.protection.outlook.com`
		A	2a01:111:f403:c902::2 ^{🇺🇸 Microsoft}
			PTR	`mail-sj0pr03cu01602.inbound.protection.outlook.com`
		A	2a01:111:f403:c92c::4 ^{🇺🇸 Microsoft}
			PTR	`mail-dm6pr05cu00404.inbound.protection.outlook.com`
		A	2a01:111:f403:f804::1 ^{🇺🇸 Microsoft}
			PTR	`mail-co1pr05cu00301.inbound.protection.outlook.com`
		A	2a01:111:f403:f805:: ^{🇺🇸 Microsoft}
			PTR	`mail-mw2pr02cu00400.inbound.protection.outlook.com`
		A	52.101.11.15^{🇺🇸 Microsoft}
			PTR	`mail-sa9pr02cu00207.inbound.protection.outlook.com`
		A	52.101.40.6^{🇺🇸 Microsoft}
			PTR	`mail-cy1pr03cu00106.inbound.protection.outlook.com`
		A	52.101.41.58^{🇺🇸 Microsoft}
			PTR	`mail-sj0pr02cu00102.inbound.protection.outlook.com`
		A	52.101.194.17^{🇺🇸 Microsoft}
			PTR	`mail-ch5pr02cu00401.inbound.protection.outlook.com`
A	2600:1f18:1503:ac00:78ab:3b1:2cdf:c9ff ^{🇺🇸 Amazon}
A	2600:1f18:1503:ac01:3e59:bfdd:78a1:8496 ^{🇺🇸 Amazon}
A	2600:1f18:1503:ac02:1576:87d0:c7a8:34e6 ^{🇺🇸 Amazon}
A	2600:1f18:1503:ac03:5280:f8a4:52f7:673b ^{🇺🇸 Amazon}
A	2600:1f18:1503:ac04:adcb:33a3:15fd:257c ^{🇺🇸 Amazon}
A	2600:1f18:1503:ac05:4785:5c59:e5a9:106b ^{🇺🇸 Amazon}
A	34.233.191.40^{🇺🇸 Amazon}
		PTR	`ec2-34-233-191-40.compute-1.amazonaws.com`
A	44.214.73.137^{🇺🇸 Amazon}
		PTR	`ec2-44-214-73-137.compute-1.amazonaws.com`
A	52.1.35.180^{🇺🇸 Amazon}
		PTR	`ec2-52-1-35-180.compute-1.amazonaws.com`
A	54.80.215.75^{🇺🇸 Amazon}
		PTR	`ec2-54-80-215-75.compute-1.amazonaws.com`
A	54.174.14.147^{🇺🇸 Amazon}
		PTR	`ec2-54-174-14-147.compute-1.amazonaws.com`
A	54.198.48.190^{🇺🇸 Amazon}
		PTR	`ec2-54-198-48-190.compute-1.amazonaws.com`

`build`

	NS	`a.nic.build`
	NS	`b.nic.build`
	NS	`c.nic.build`
	NS	`d.nic.build`

Starts with same word
`nostr.es`
`nostr.ie`
`nostr.band`
`nostr.com`
`nostr.net`
`nostr.build`
`nostr.mom`
`nostr.info`
`nostr.how`
`nostr.land`

Starts similarily
`nstro.us`
`nostr.com`
`sornt.com`
`storn.fr`
`ornst.com`
`storn.eu`
`onrts.com`
`snort.com`
`nostr.net`
`stron.com`
`snort.de`
`notrs.net`
`norst.org`
`notrs.com`
`snort.ca`
`notrs.co`
`ronts.com`
`snort.at`
`stron.kz`
`nstro.com`
`sntor.com`
`ornts.ru`
`onstr.ru`
`trons.com`
`nstor.com`
`storn.co`
`stron.net`
`notrs.us`
`tsorn.de`
`ronts.nl`
`snort.org`
`nstor.ru`
`ntros.com`
`nostr.build`
`nsort.com`
`rstno.ru`
`storn.no`
`stron.com.tw`
`nostr.mom`
`snort.info`
`trons.biz`
`nosrt.org`
`nostr.info`
`stron.ru`
`tnsor.de`
`ortns.com`
`nostr.how`
`nostr.land`
`stonr.com`
`tsorn.com`
`stron.ee`
`torns.net`
`snort.us`
`trons.net`
`snotr.net`
`stnor.com`
`nostr.es`
`snort.eu`
`nostr.ie`
`nostr.band`
`snort.it`
`storn.com`
`snort.me`
`snort.fr`
`rosnt.ru`
`notrs.org`
`stron.zone`
`tnsor.com`
`storn.de`
`snort.net`
`snotr.ru`
`trons.se`
`ortns.org`

AI analysis

The DNS record nostr.build resolves to a list of twelve IP addresses: 2600:1f18:1503:ac00:78ab:3b1:2cdf:c9ff, 2600:1f18:1503:ac01:3e59:bfdd:78a1:8496, 2600:1f18:1503:ac02:1576:87d0:c7a8:34e6, 2600:1f18:1503:ac03:5280:f8a4:52f7:673b, 2600:1f18:1503:ac04:adcb:33a3:15fd:257c, 2600:1f18:1503:ac05:4785:5c59:e5a9:106b, 34.233.191.40, 44.214.73.137, 52.1.35.180, 54.80.215.75, 54.174.14.147, and 54.198.48.190.

For example, IP numbers are shared between ec2-52-1-35-180.compute-1.amazonaws.com and other host names like nostr.build.

Four name servers, ns-411.awsdns-51.com, ns-749.awsdns-29.net, ns-1326.awsdns-37.org, and ns-1933.awsdns-49.co.uk, are responsible for the delegation of nostr.build.

The domain nostr.build shares its name servers at least partially with other domains such as ibossconnect.com, sunflare.com, erkrath-spd.de, columbiapsychiatry.org, and grupobaugam.org.

The name servers ns-1142.awsdns-14.org, ns-1908.awsdns-46.co.uk, ns-711.awsdns-24.net, ns-691.awsdns-22.net, ns-1028.awsdns-00.org, ns-1864.awsdns-41.co.uk, ns-24.awsdns-03.com, ns-483.awsdns-60.com, ns-408.awsdns-51.com, and ns-1611.awsdns-09.co.uk are often used in conjunction.

ns-411.awsdns-51.com, 2600:9000:5301:9b00::1, and 205.251.193.155 are associated together.

ns-749.awsdns-29.net, 2600:9000:5302:ed00::1, and 205.251.194.237 are linked.

ns-1326.awsdns-37.org, 2600:9000:5305:2e00::1, and 205.251.197.46 are connected.

ns-1933.awsdns-49.co.uk, 2600:9000:5307:8d00::1, and 205.251.199.141 are paired.

The mail server nostr-build.mail.protection.outlook.com is responsible for handling nostr.build.

The DNS record nostr-build.mail.protection.outlook.com resolves to the following eight IP addresses: 2a01:111:f403:c902::2, 2a01:111:f403:c92c::4, 2a01:111:f403:f804::1, 2a01:111:f403:f805::, 52.101.11.15, 52.101.40.6, 52.101.41.58, and 52.101.194.17.

dbq