DNSWHOIS.INFO - securityblue.team

Search for IP or hostnames:

securityblue.team checked at 2025-10-28T20:31:58.381Z 261ms 127/127/127 100% R:15

`securityblue.team`

NS	`ns-378.awsdns-47.com`
		A	2600:9000:5301:7a00::1 ^{🇺🇸 Amazon}
			PTR	`ns-378.awsdns-47.com`
		A	205.251.193.122^{🇺🇸 Amazon}
			PTR	`ns-378.awsdns-47.com`
NS	`ns-901.awsdns-48.net`
		A	2600:9000:5303:8500::1 ^{🇺🇸 Amazon}
			PTR	`ns-901.awsdns-48.net`
		A	205.251.195.133^{🇺🇸 Amazon}
			PTR	`ns-901.awsdns-48.net`
NS	`ns-1044.awsdns-02.org`
		A	2600:9000:5304:1400::1 ^{🇺🇸 Amazon}
			PTR	`ns-1044.awsdns-02.org`
		A	205.251.196.20^{🇺🇸 Amazon}
			PTR	`ns-1044.awsdns-02.org`
NS	`ns-1768.awsdns-29.co.uk`
		A	2600:9000:5306:e800::1 ^{🇺🇸 Amazon}
			PTR	`ns-1768.awsdns-29.co.uk`
		A	205.251.198.232^{🇺🇸 Amazon}
			PTR	`ns-1768.awsdns-29.co.uk`
MX	`securityblue-team.mail.protection.outlook.com`
		A	2a01:111:f403:ca0b::1 ^{🇬🇧 Microsoft}
			PTR	`mail-lo3p265cu00301.inbound.protection.outlook.com`
		A	2a01:111:f403:ca0b::2 ^{🇬🇧 Microsoft}
			PTR	`mail-lo0p265cu00202.inbound.protection.outlook.com`
		A	2a01:111:f403:ca1a:: ^{🇬🇧 Microsoft}
			PTR	`mail-cwxp265cu00500.inbound.protection.outlook.com`
		A	2a01:111:f403:ca1a::1 ^{🇬🇧 Microsoft}
			PTR	`mail-cwxp265cu00601.inbound.protection.outlook.com`
		A	52.101.89.0^{🇬🇧 Microsoft}
			PTR	`mail-lo2p265cu02300.inbound.protection.outlook.com`
		A	52.101.89.1^{🇬🇧 Microsoft}
			PTR	`mail-lo0p265cu00201.inbound.protection.outlook.com`
		A	52.101.89.2^{🇬🇧 Microsoft}
			PTR	`mail-lo3p265cu00302.inbound.protection.outlook.com`
		A	52.101.99.0^{🇬🇧 Microsoft}
			PTR	`mail-cwxp265cu00600.inbound.protection.outlook.com`
A	99.86.114.47
		PTR	`server-99-86-114-47.lhr61.r.cloudfront.net`
A	99.86.114.57
		PTR	`server-99-86-114-57.lhr61.r.cloudfront.net`
A	99.86.114.80
		PTR	`server-99-86-114-80.lhr61.r.cloudfront.net`
A	99.86.114.121
		PTR	`server-99-86-114-121.lhr61.r.cloudfront.net`

`team`

	NS	`v0n0.nic.team`
	NS	`v0n1.nic.team`
	NS	`v0n2.nic.team`
	NS	`v0n3.nic.team`
	NS	`v2n0.nic.team`
	NS	`v2n1.nic.team`

Starts with same word

securityblue.team

Starts similarily

bluesecurity.com.br

bluesecurity.com

bluesecurity.co.za

securityblue.team

bleusecurity.com

AI analysis

Four IP numbers are pointed to by securityblue.team: 99.86.114.47, 99.86.114.57, 99.86.114.80 and 99.86.114.121.

Other host names, for instance server-99-86-114-121.lhr61.r.cloudfront.net, server-99-86-114-57.lhr61.r.cloudfront.net, server-99-86-114-80.lhr61.r.cloudfront.net and server-99-86-114-47.lhr61.r.cloudfront.net share IP numbers with securityblue.team.

securityblue.team is delegated to four name servers: ns-378.awsdns-47.com, ns-901.awsdns-48.net, ns-1044.awsdns-02.org and ns-1768.awsdns-29.co.uk.

securityblue.team at least partially shares name servers with other domains, for instance suzuden.co.jp, preprod.internal.gradecapture.ocr.org.uk, s4ye.com, nou.co and nichihos.co.jp.

These name servers are commonly used with ns-152.awsdns-19.com, ns-890.awsdns-47.net, ns-1281.awsdns-32.org, ns-1428.awsdns-50.org and ns-1255.awsdns-28.org.

Host names with two IP numbers:

ns-378.awsdns-47.com points to 2600:9000:5301:7a00::1 and 205.251.193.122; ns-901.awsdns-48.net points to 2600:9000:5303:8500::1 and 205.251.195.133; ns-1044.awsdns-02.org points to 2600:9000:5304:1400::1 and 205.251.196.20; ns-1768.awsdns-29.co.uk points to 2600:9000:5306:e800::1 and 205.251.198.232.

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

Host securityblue-team.mail.protection.outlook.com points to eight IP numbers: 2a01:111:f403:ca0b::1, 2a01:111:f403:ca0b::2, 2a01:111:f403:ca1a::, 2a01:111:f403:ca1a::1, 52.101.89.0, 52.101.89.1, 52.101.89.2 and 52.101.99.0.

dbq