CF1757699918380-tsm20250912070358

IPLIST.NET - nohijacking.com

Search for IP or hostnames:

nohijacking.com checked at 2025-09-12T17:58:38.289Z 1157ms 133/133/133 100% R:18

nohijacking.com

NSns303.dnsever.com
A91.134.148.217🇫🇷 OVH
PTRns303.dnsever.com
NSns321.dnsever.com
A15.235.2.97🇨🇦 OVH
PTRns321.dnsever.com
NSns346.dnsever.com
A5.39.12.230🇫🇷 OVH
PTRns346.dnsever.com
NSns367.dnsever.com
A91.134.148.199🇫🇷 OVH
PTRns17.dnsever.com
NSns382.dnsever.com
A51.38.97.136🇫🇷 OVH
PTRns382.dnsever.com
MXaspmx2.googlemail.com
A2a00:1450:4013:c1c::1b 🇳🇱 Google
PTRyugrqog-in-f27.1e100.net
A192.178.156.27🇺🇸 Google
PTRyugrqog-in-f27.1e100.net
MXaspmx3.googlemail.com
A2a00:1450:4025:c01::1a 🇵🇱 Google
PTRrd-in-f26.1e100.net
A142.250.147.27🇺🇸 Google
PTRrd-in-f27.1e100.net
MXaspmx.l.google.com
A2607:f8b0:4023:c0b::1a 🇺🇸 Google
PTRdd-in-f26.1e100.net
A142.250.101.27🇺🇸 Google
PTRdz-in-f27.1e100.net
MXalt1.aspmx.l.google.com
A2607:f8b0:4023:100f::1b 🇺🇸 Google
PTRyudfwra-in-f27.1e100.net
A192.178.220.26🇺🇸 Google
PTRyudfwra-in-f26.1e100.net
MXalt2.aspmx.l.google.com
A2607:f8b0:4003:c0a::1a 🇺🇸 Google
PTRol-in-x1a.1e100.net
PTRpb-in-f26.1e100.net
A142.251.190.26🇺🇸 Google
PTRpb-in-f26.1e100.net
A2404:6800:4001:813::2013 🇦🇺 Google
PTRpnkula-ad-in-x13.1e100.net
A172.217.25.243🇺🇸 Google
PTRnrt12s14-in-f19.1e100.net
PTRnrt12s14-in-f243.1e100.net
PTRpnkula-ad-in-f19.1e100.net

com

NSa.gtld-servers.net
NSb.gtld-servers.net
NSc.gtld-servers.net
NSd.gtld-servers.net
NSe.gtld-servers.net
NSf.gtld-servers.net
NSg.gtld-servers.net
NSh.gtld-servers.net
NSi.gtld-servers.net
NSj.gtld-servers.net
NSk.gtld-servers.net
NSl.gtld-servers.net
NSm.gtld-servers.net

Starts with same word

Starts similarily

AI analysis

nohijacking.com is configured to point to two IP addresses: 2404:6800:4001:813::2013 and 172.217.25.243.

IP numbers are shared between nohijacking.com and other host names such as nrt12s14-in-f19.1e100.net, pnkula-ad-in-f19.1e100.net, and nrt12s14-in-f243.1e100.net.

Five name servers, ns303.dnsever.com, ns321.dnsever.com, ns346.dnsever.com, ns367.dnsever.com, and ns382.dnsever.com, are delegated to nohijacking.com.

The domain nohijacking.com partially shares its name servers with other domains such as creat.or.kr, memoriant.com, dhy79.com, 38778.com, and saiborder.com.

The name servers ns348.dnsever.com, ns304.dnsever.com, ns369.dnsever.com, ns322.dnsever.com, ns305.dnsever.com, ns325.dnsever.com, ns385.dnsever.com, ns331.dnsever.com, ns308.dnsever.com, and ns364.dnsever.com are frequently used in conjunction.

IP number 91.134.148.217 is pointed to by ns303.dnsever.com.

IP number 15.235.2.97 is pointed to by ns321.dnsever.com.

IP number 5.39.12.230 is pointed to by ns346.dnsever.com.

IP number 91.134.148.199 is pointed to by ns367.dnsever.com.

IP number 51.38.97.136 is pointed to by ns382.dnsever.com.

Five mail servers, aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com, alt1.aspmx.l.google.com, and alt2.aspmx.l.google.com, are responsible for handling nohijacking.com.

Other domains such as baikakudo.jp, selco-india.com, paffloff.com, goodfunction.net, and boznikmandm.com share at least partially some mail servers with nohijacking.com.

The mail servers aspmx4.googlemail.com, aspmx5.googlemail.com, alt3.aspmx.l.google.com, and alt4.aspmx.l.google.com are commonly utilized in conjunction.

aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com, alt1.aspmx.l.google.com, and alt2.aspmx.l.google.com each point to two IP numbers respectively: 2a00:1450:4013:c1c::1b, 192.178.156.27; 2a00:1450:4025:c01::1a, 142.250.147.27; 2607:f8b0:4023:c0b::1a, 142.250.101.27; 2607:f8b0:4023:100f::1b, 192.178.220.26; 2607:f8b0:4003:c0a::1a, 142.251.190.26.

Perform reverse DNS lookup as well as normal forward DNS. Check Autonomous System Numbers (ASNs) and BGP connections between Internet Service Providers.
dbq

QnPeLcs CF johedugfp 2025-09-12