DNSWHOIS.INFO - ragingwaves.com

Search for IP or hostnames:

ragingwaves.com checked at 2025-10-26T07:36:07.557Z 436ms 141/141/141 100% R:16

`ragingwaves.com`

NS	`ns20.digicertdns.com`
		A	2600:1800:10::1:1f ^{🇺🇸 Tiggee}
			PTR	`ns20.digicertdns.com`
		A	208.94.148.223^{🇺🇸 Tiggee}
			PTR	`ns20.digicertdns.com`
NS	`ns21.digicertdns.com`
		A	2600:1801:11::1:1f ^{🇺🇸 Tiggee}
			PTR	`ns21.digicertdns.com`
		A	208.80.124.223^{🇺🇸 Tiggee}
			PTR	`ns21.digicertdns.com`
NS	`ns22.digicertdns.com`
		A	2600:1802:12::1:1f ^{🇺🇸 Tiggee}
			PTR	`ns22.digicertdns.com`
		A	208.80.126.223^{🇺🇸 Tiggee}
			PTR	`ns22.digicertdns.com`
NS	`ns23.digicertdns.net`
		A	2600:1801:13::1:1f ^{🇺🇸 Tiggee}
			PTR	`ns23.digicertdns.net`
		A	208.80.125.223^{🇺🇸 Tiggee}
			PTR	`ns23.digicertdns.net`
NS	`ns24.digicertdns.net`
		A	2600:1802:14::1:1f ^{🇺🇸 Tiggee}
			PTR	`ns24.digicertdns.net`
		A	208.80.127.223^{🇺🇸 Tiggee}
			PTR	`ns24.digicertdns.net`
NS	`ns25.digicertdns.net`
		A	2600:1800:15::1:1f ^{🇺🇸 Tiggee}
			PTR	`ns25.digicertdns.net`
		A	208.94.149.223^{🇺🇸 Tiggee}
			PTR	`ns25.digicertdns.net`
MX	`ragingwaves-com.mail.protection.outlook.com`
		A	2a01:111:f403:c903:: ^{🇺🇸 Microsoft}
			PTR	`mail-co1pr03cu00100.inbound.protection.outlook.com`
		A	2a01:111:f403:c946::3 ^{🇺🇸 Microsoft}
			PTR	`mail-ch0pr04cu00603.inbound.protection.outlook.com`
		A	2a01:111:f403:f902::1 ^{🇺🇸 Microsoft}
			PTR	`mail-bl2pr02cu00101.inbound.protection.outlook.com`
		A	2a01:111:f403:f908::1 ^{🇺🇸 Microsoft}
			PTR	`mail-bn1pr04cu00101.inbound.protection.outlook.com`
		A	52.101.9.11^{🇺🇸 Microsoft}
			PTR	`mail-bl2pr04cu00103.inbound.protection.outlook.com`
		A	52.101.10.10^{🇺🇸 Microsoft}
			PTR	`mail-bn8pr05cu00102.inbound.protection.outlook.com`
		A	52.101.40.1^{🇺🇸 Microsoft}
			PTR	`mail-cy4pr03cu00101.inbound.protection.outlook.com`
		A	52.101.42.13^{🇺🇸 Microsoft}
			PTR	`mail-mw2pr02cu00405.inbound.protection.outlook.com`
A	141.193.213.20^{🇺🇸 Cloudflare London}
A	141.193.213.21^{🇺🇸 Cloudflare London}

`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`

rank #835362 globally
rank #435695 in the tld

Starts with same word

ragingwaves.com

Starts similarily

ragingwaves.com

AI analysis

ragingwaves.com resolves to two IP numbers: 141.193.213.20 and 141.193.213.21.

Other host names, for instance northhillsauto.com, redhype.com, centuryliquorandwines.com, fleishman-hillard.com and consultants.actionable.co share IP numbers with ragingwaves.com.

ragingwaves.com is delegated to six name servers: ns20.digicertdns.com, ns21.digicertdns.com, ns22.digicertdns.com, ns23.digicertdns.net, ns24.digicertdns.net and ns25.digicertdns.net.

ragingwaves.com shares some name servers with other domains, for example kclsed.org, glfs.com, helppetout.ch, employerinsuranceenroll.com and cloenix.com.

These name servers are often used together with pdns196.ultradns.biz, pdns196.ultradns.com and pdns196.ultradns.net.

Host names with two IP numbers:

ns20.digicertdns.com -> 2600:1800:10::1:1f and 208.94.148.223

ns21.digicertdns.com -> 2600:1801:11::1:1f and 208.80.124.223

ns22.digicertdns.com -> 2600:1802:12::1:1f and 208.80.126.223

ns23.digicertdns.net -> 2600:1801:13::1:1f and 208.80.125.223

ns24.digicertdns.net -> 2600:1802:14::1:1f and 208.80.127.223

ns25.digicertdns.net -> 2600:1800:15::1:1f and 208.94.149.223

ragingwaves.com is handled by a single mail server, ragingwaves-com.mail.protection.outlook.com.

Host ragingwaves-com.mail.protection.outlook.com points to eight IP numbers: 2a01:111:f403:c903::, 2a01:111:f403:c946::3, 2a01:111:f403:f902::1, 2a01:111:f403:f908::1, 52.101.9.11, 52.101.10.10, 52.101.40.1 and 52.101.42.13.

dbq