CF1762443211482-tsm20251105200708

DNSWHOIS.INFO - mybrickbot.com

Search for IP or hostnames:

mybrickbot.com checked at 2025-11-06T15:33:31.446Z 696ms 115/115/115 100% R:15

`mybrickbot.com`

	NS	`ns63.domaincontrol.com`
			A	2603:5:2154::2a ^{🇺🇸 GODADDY-DNS-GLOBAL}
				PTR	`ns63.domaincontrol.com`
			A	97.74.101.42^{🇺🇸 GODADDY-DNS-GLOBAL}
				PTR	`ns63.domaincontrol.com`
	NS	`ns64.domaincontrol.com`
			A	2603:5:2254::2a ^{🇺🇸 GODADDY-DNS-GLOBAL}
				PTR	`ns64.domaincontrol.com`
			A	173.201.69.42^{🇺🇸 GODADDY-DNS-GLOBAL}
				PTR	`ns64.domaincontrol.com`
	MX	`aspmx.l.google.com`
			A	2607:f8b0:4004:c19::1a ^{🇺🇸 Google}
				PTR	`bk-in-f26.1e100.net`
			A	142.251.179.27^{🇺🇸 Google}
				PTR	`pd-in-f27.1e100.net`
	MX	`alt1.aspmx.l.google.com`
			A	2a00:1450:400b:c02::1b ^{🇮🇪 Google}
				PTR	`dj-in-f27.1e100.net`
			A	172.253.116.27^{🇺🇸 Google}
				PTR	`dj-in-f27.1e100.net`
	MX	`alt2.aspmx.l.google.com`
			A	2a00:1450:400c:c00::1a ^{🇧🇪 Google}
				PTR	`ws-in-f26.1e100.net`
				PTR	`ws-in-x1a.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.27^{🇺🇸 Google}
				PTR	`rb-in-f27.1e100.net`
	MX	`alt4.aspmx.l.google.com`
			A	2a00:1450:4013:c1e::1b ^{🇳🇱 Google}
				PTR	`yugrqzs-in-f27.1e100.net`
			A	192.178.213.26^{🇺🇸 Google}
				PTR	`yugrqzs-in-f26.1e100.net`
	A	121.243.26.109^{🇮🇳 Tata Communications AS4755}
			PTR	`121.243.26.109.static-delhi.vsnl.net.in`

`com`

	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`

Starts with same word

mybrickbot.com

Starts similarily

mybrickbot.com

AI analysis

mybrickbot.com resolves to a single IP: 121.243.26.109.

mybrickbot.com has two name servers: ns63.domaincontrol.com and ns64.domaincontrol.com.

mybrickbot.com shares the same name server setup as other domains, for example virgemsjewelry.com, kottermundjewelers.com, itsapiglife.com, nebuone.com and wdym.in.

mybrickbot.com partially shares name servers with other domains, for instance pid.at.

Host names with two IP numbers:

ns63.domaincontrol.com points to: 2603:5:2154::2a and 97.74.101.42; ns64.domaincontrol.com points to: 2603:5:2254::2a and 173.201.69.42.

mybrickbot.com is handled by 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.

mybrickbot.com shares some mail servers with other domains, at least partially; for instance our.today, pinoypub.ph, rogeldiamonds.co.il, gastrouni.com and montuori.net.

these mail servers are commonly used alongside aspmx3.googlemail.com and aspmx2.googlemail.com.

Host names with two IPs:

Host aspmx.l.google.com has IPs 2607:f8b0:4004:c19::1a and 142.251.179.27.

Host alt1.aspmx.l.google.com has IPs 2a00:1450:400b:c02::1b and 172.253.116.27.

Host alt2.aspmx.l.google.com has IPs 2a00:1450:400c:c00::1a and 173.194.76.27.

Host alt3.aspmx.l.google.com has IPs 2a00:1450:4025:402::1a and 142.250.102.27.

Host alt4.aspmx.l.google.com has IPs 2a00:1450:4013:c1e::1b and 192.178.213.26.

dbq