DNSWHOIS.INFO - orbelog.com

Search for IP or hostnames:

orbelog.com checked at 2025-11-04T07:10:11.884Z 693ms 116/116/116 100% R:14

`orbelog.com`

NS	`ns-394.awsdns-49.com`
		A	2600:9000:5301:8a00::1 ^{🇺🇸 Amazon}
			PTR	`ns-394.awsdns-49.com`
		A	205.251.193.138^{🇺🇸 Amazon}
			PTR	`ns-394.awsdns-49.com`
NS	`ns-847.awsdns-41.net`
		A	2600:9000:5303:4f00::1 ^{🇺🇸 Amazon}
			PTR	`ns-847.awsdns-41.net`
		A	205.251.195.79^{🇺🇸 Amazon}
			PTR	`ns-847.awsdns-41.net`
NS	`ns-1096.awsdns-09.org`
		A	2600:9000:5304:4800::1 ^{🇺🇸 Amazon}
			PTR	`ns-1096.awsdns-09.org`
		A	205.251.196.72^{🇺🇸 Amazon}
			PTR	`ns-1096.awsdns-09.org`
NS	`ns-1782.awsdns-30.co.uk`
		A	2600:9000:5306:f600::1 ^{🇺🇸 Amazon}
			PTR	`ns-1782.awsdns-30.co.uk`
		A	205.251.198.246^{🇺🇸 Amazon}
			PTR	`ns-1782.awsdns-30.co.uk`
MX	`orbelog-com.mail.protection.outlook.com`
		A	2a01:111:f403:c903:: ^{🇺🇸 Microsoft}
			PTR	`mail-co1pr03cu00100.inbound.protection.outlook.com`
		A	2a01:111:f403:c927:: ^{🇺🇸 Microsoft}
			PTR	`mail-bn6pr21cu00500.inbound.protection.outlook.com`
		A	2a01:111:f403:c931::1 ^{🇺🇸 Microsoft}
			PTR	`mail-sa9pr03cu00201.inbound.protection.outlook.com`
		A	2a01:111:f403:f912:: ^{🇺🇸 Microsoft}
			PTR	`mail-cy5pr03cu00200.inbound.protection.outlook.com`
		A	52.101.9.11^{🇺🇸 Microsoft}
			PTR	`mail-bl2pr04cu00103.inbound.protection.outlook.com`
		A	52.101.10.16^{🇺🇸 Microsoft}
			PTR	`mail-bn6pr21cu00500.inbound.protection.outlook.com`
		A	52.101.42.18^{🇺🇸 Microsoft}
			PTR	`mail-co1pr03cu00302.inbound.protection.outlook.com`
		A	52.101.194.0^{🇺🇸 Microsoft}
			PTR	`mail-ch5pr02cu00200.inbound.protection.outlook.com`
A	184.168.131.241^{🇺🇸 GODADDY}
		PTR	`241.131.168.184.host.secureserver.net`

`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

orbelog.com

Starts similarily

bologer.ru

eroblog.de

bergolo.com

blooger.de

broogle.com

blooger.blogspot.mx

blogero.com

roboleg.com

orbelog.com

obloger.ru

goobler.com

gloober.com

eroblog.nl

borelog.com

blooger.pl

blogero.pl

legobro.com

broogle.de

eroblog.net

bergolo.it

globero.hu

gelboor.com

reglobo.com

globore.com

globero.hr

oreblog.com

blogore.com

bolergo.com

broogle.net

belogor.com

robelog.com

bogreol.dk

boolger.blogspot.nl

blooger.com

bergolo.org

blooger.net

AI analysis

orbelog.com resolves to one IP number: 184.168.131.241.

Other host names, for instance ojsneb.com, mltalent.com, pctcelltherapy.com, zales.org and bryan-j.com share IP numbers with orbelog.com.

orbelog.com delegates to four name servers: ns-394.awsdns-49.com, ns-847.awsdns-41.net, ns-1096.awsdns-09.org and ns-1782.awsdns-30.co.uk.

orbelog.com at least partially shares name servers with other domains, including rideshareonline.com, flowerstreatment.com, escala.jp, 27.247.194.in-addr.arpa and afelogistics.com.

these name servers are commonly used with ns-287.awsdns-35.com, ns-1292.awsdns-33.org, ns-1873.awsdns-42.co.uk, ns-687.awsdns-21.net, ns-652.awsdns-17.net, ns-443.awsdns-55.com, ns-529.awsdns-02.net, ns-1509.awsdns-60.org and ns-2037.awsdns-62.co.uk.

Host names with two IP numbers: ns-394.awsdns-49.com points to 2600:9000:5301:8a00::1 and 205.251.193.138; ns-847.awsdns-41.net points to 2600:9000:5303:4f00::1 and 205.251.195.79; ns-1096.awsdns-09.org points to 2600:9000:5304:4800::1 and 205.251.196.72; ns-1782.awsdns-30.co.uk points to 2600:9000:5306:f600::1 and 205.251.198.246.

A single mail server handles orbelog.com, orbelog-com.mail.protection.outlook.com.

Host orbelog-com.mail.protection.outlook.com points to eight IPs: 2a01:111:f403:c903::, 2a01:111:f403:c927::, 2a01:111:f403:c931::1, 2a01:111:f403:f912::, 52.101.9.11, 52.101.10.16, 52.101.42.18 and 52.101.194.0.

dbq