WWW.RTSAK.COM - netsec.expert

Search for IP or hostnames:

netsec.expert checked at 2025-09-11T03:31:08.389Z 225ms 146/146/146 100% R:17

`netsec.expert`

NS	`ns-cloud-c1.googledomains.com`
		A	2001:4860:4802:32::6c ^{🇺🇸 Google}
			PTR	`ns-cloud-c1.googledomains.com`
		A	216.239.32.108^{🇺🇸 Google}
			PTR	`ns-cloud-c1.googledomains.com`
NS	`ns-cloud-c2.googledomains.com`
		A	2001:4860:4802:34::6c ^{🇺🇸 Google}
			PTR	`ns-cloud-c2.googledomains.com`
		A	216.239.34.108^{🇺🇸 Google}
			PTR	`ns-cloud-c2.googledomains.com`
NS	`ns-cloud-c3.googledomains.com`
		A	2001:4860:4802:36::6c ^{🇺🇸 Google}
			PTR	`ns-cloud-c3.googledomains.com`
		A	216.239.36.108^{🇺🇸 Google}
			PTR	`ns-cloud-c3.googledomains.com`
NS	`ns-cloud-c4.googledomains.com`
		A	2001:4860:4802:38::6c ^{🇺🇸 Google}
			PTR	`ns-cloud-c4.googledomains.com`
		A	216.239.38.108^{🇺🇸 Google}
			PTR	`ns-cloud-c4.googledomains.com`
MX	`aspmx.l.google.com`
		A	2607:f8b0:4004:c1b::1b ^{🇺🇸 Google}
			PTR	`wv-in-f27.1e100.net`
		A	64.233.180.27^{🇺🇸 Google}
			PTR	`on-in-f27.1e100.net`
			PTR	`pe-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`
		A	2a00:1450:400b:c02::1a ^{🇮🇪 Google}
			PTR	`dj-in-f26.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::1b ^{🇳🇱 Google}
			PTR	`rb-in-f27.1e100.net`
		A	142.250.102.26^{🇺🇸 Google}
			PTR	`rb-in-f26.1e100.net`
A	185.199.108.153^{🇺🇸 Fastly}
		PTR	`cdn-185-199-108-153.github.com`
A	185.199.109.153^{🇺🇸 Fastly}
		PTR	`cdn-185-199-109-153.github.com`
A	185.199.110.153^{🇺🇸 Fastly}
		PTR	`cdn-185-199-110-153.github.com`
A	185.199.111.153^{🇺🇸 Fastly}
		PTR	`cdn-185-199-111-153.github.com`

`expert`

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

Up
`www.netsec.expert`

Starts with same word
`netsec.ch`
`netsec.ru`
`netsec.co.za`
`netsec.news`
`netsec.ro`
`netsec.cz`
`netsec.com.mx`
`netsec.co.il`
`netsec.us`
`netsec.pw`
`netsec.tools`
`netsec.pro`
`netsec.hu`
`netsec.fi`
`netsec.ca`
`netsec.net`
`netsec.at`
`netsec.cloud`
`netsec.nl`
`netsec.com`
`netsec.cc`
`netsec.be`
`netsec.com.tr`
`netsec.sk`
`netsec.co`
`netsec.expert`
`netsec.de`
`netsec.dk`
`netsec.cl`
`netsec.gr`
`netsec.se`
`netsec.eu`
`netsec.ws`
`netsec.rs`
`netsec.xyz`
`netsec.me`

Starts similarily
`sentec.ca`
`escnet.com.au`
`escent.it`
`netsec.news`
`tsence.com`
`sentec.it`
`cesnet.org`
`secnet.co.nz`
`netsec.ro`
`encest.com`
`sentec.de`
`scenet.de`
`ecents.net`
`netsec.cz`
`escent.be`
`sentec.at`
`netecs.de`
`sentec.ru`
`escent.ro`
`netsec.com.mx`
`secnet.net.au`
`nestec.eu`
`nestec.de`
`netsec.co.il`
`netsec.us`
`netsec.pw`
`ctenes.best`
`enstec.com`
`secnet.pro`
`enstec.co.kr`
`cseent.com`
`cenest.net`
`scenet.co.jp`
`secnet.info`
`secnet.cl`
`centes.net`
`cesnet.cz`
`nestec.at`
`netsec.tools`
`netsec.pro`
`scente.com`
`tensec.net`
`netsec.hu`
`secnet.no`
`secnet.at`
`netsec.fi`
`tensec.com`
`netecs.org`
`entsec.co.uk`
`ecsnet.at`
`secnet.dk`
`scenet.com`
`secnet.com`
`csteen.dk`
`sentec.nl`
`secnet.co.jp`
`cesnet.net`
`tesnec.com`
`sentec.be`
`netcse.com`
`sentec.es`
`escent.info`
`netecs.pl`
`tecnes.com`
`teensc.com`
`escent.de`
`netsec.ca`
`netsec.net`
`sentec.co.kr`
`netsec.at`
`sentec.org`
`ecnets.com`
`enetcs.com`
`tecsen.com.my`
`sentec.fr`
`senect.com`
`netsec.cloud`
`nestec.org`
`netsec.nl`
`centes.eu`
`secnet.pl`
`ecsnet.ro`
`secnet.de`
`tenecs.org`
`sentec.ch`
`cesnet.com`
`ceestn.com`
`secnet.online`
`secnet.com.pl`
`netecs.com`
`secnet.co.zw`
`nestec.pl`
`ecents.us`
`sentec.net`
`sentec.ro`
`escnet.net.au`
`netsec.com`
`stence.com`
`teensc.org`
`nestec.jp`

AI analysis

The parent of www.netsec.expert is netsec.expert.

netsec.expert is configured to point to the following four IP addresses: 185.199.108.153, 185.199.109.153, 185.199.110.153, and 185.199.111.153.

IP numbers are shared between netsec.expert and other host names, such as sidanta.lt, eitanlees.github.io, omyradio.net, jiewong42.github.io, and cokepokes.github.io.

Four name servers, ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, and ns-cloud-c4.googledomains.com, have been delegated to netsec.expert.

The domain netsec.expert shares name servers, at least partially, with other domains such as itslovelyb.com, aspira.co, rosemarra.com, oepping.com, and nasirautos.com.

The name servers ns-127.awsdns-15.com, ns-664.awsdns-19.net, ns-1424.awsdns-50.org, and ns-1660.awsdns-15.co.uk are frequently utilized in conjunction.

ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, and ns-cloud-c4.googledomains.com all point to two IP numbers each: 2001:4860:4802:32::6c and 216.239.32.108; 2001:4860:4802:34::6c and 216.239.34.108; 2001:4860:4802:36::6c and 216.239.36.108; 2001:4860:4802:38::6c and 216.239.38.108, respectively.

The handling of netsec.expert is managed by four mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, and alt3.aspmx.l.google.com.

Other domains like thoss.org, glamclub.net, adambonner.co.uk, global-gardens.org, and mailexchangeandmore.com share some mail servers, at least partially, with netsec.expert.

The mail servers alt4.aspmx.l.google.com are commonly utilized in conjunction with these mail servers.

aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, and alt3.aspmx.l.google.com all point to two IP numbers each: 2607:f8b0:4004:c1b::1b and 64.233.180.27; 2a00:1450:400b:c02::1a and 172.253.116.27; 2a00:1450:400c:c00::1a and 173.194.76.27; 2a00:1450:4025:402::1b and 142.250.102.26, respectively.

dbq