pifagor.kz checked at 2025-03-15T14:30:37.674Z 244ms 129/129/129 100% R:15
DNS.NINJA - pifagor.kz
Search for IP or hostnames
pifagor.kz
NS | ns1.ps.kz | ||||||
A | 2a00:5da0:0:1::194 🇰🇿 PS Internet Company Network | ||||||
PTR | ns1.ps.kz | ||||||
A | 195.210.46.194🇰🇿 PS Internet Company Network | ||||||
PTR | ns1.ps.kz | ||||||
NS | ns2.ps.kz | ||||||
A | 2a00:5da0:1:1::172 🇰🇿 PS Internet Company Network | ||||||
A | 195.210.46.172🇰🇿 PS Internet Company Network | ||||||
NS | ns3.ps.kz | ||||||
A | 31.210.174.104🇰🇿 PSKZ-AST | ||||||
PTR | ns3.ps.kz | ||||||
MX | aspmx.l.google.com | ||||||
A | 2a00:1450:400c:c1d::1a 🇧🇪 Google | ||||||
PTR | wh-in-f26.1e100.net | ||||||
A | 142.251.168.26🇺🇸 Google | ||||||
PTR | wh-in-f26.1e100.net | ||||||
MX | 626ssi2njzexbiy2t3ehbybq25sqcu4am767kcmqfhx2463gfrtq.mx-verification.google.com | ||||||
MX | alt1.aspmx.l.google.com | ||||||
A | 2a00:1450:4013:c16::1a 🇳🇱 Google | ||||||
PTR | ea-in-f26.1e100.net | ||||||
A | 142.250.153.26🇺🇸 Google | ||||||
PTR | ea-in-f26.1e100.net | ||||||
MX | alt2.aspmx.l.google.com | ||||||
A | 2a00:1450:4025:c03::1a 🇵🇱 Google | ||||||
PTR | rc-in-f26.1e100.net | ||||||
A | 142.251.9.27🇺🇸 Google | ||||||
PTR | rc-in-f27.1e100.net | ||||||
MX | alt3.aspmx.l.google.com | ||||||
A | 2a00:1450:4025:401::1b 🇳🇱 Google | ||||||
PTR | ra-in-f27.1e100.net | ||||||
A | 142.250.27.27🇺🇸 Google | ||||||
PTR | ra-in-f27.1e100.net | ||||||
MX | alt4.aspmx.l.google.com | ||||||
A | 2a00:1450:4013:c16::1a 🇳🇱 Google | ||||||
PTR | ea-in-f26.1e100.net | ||||||
A | 142.250.153.27🇺🇸 Google | ||||||
PTR | ea-in-f27.1e100.net | ||||||
A | 213.130.74.45🇫🇮 tilda-ie-1 |
kz
NS | ns1.nic.kz | ||||||
NS | ns2.nic.kz | ||||||
NS | ns.nic.kz |
0 | ||||
0 | ||||
0 | ||||
0 | ||||
1 | ||||
(u) | intranet.pifagor.kz | |||
8 | ||||
(lm) | pifagor.info | |||
(lm) | pifagor.org | |||
(lm) | pifagor.io | |||
(lm) | pifagor.su | |||
(lm) | pifagor.kz | |||
(lm) | pifagor.com | |||
(lm) | pifagor.ru | |||
(lm) | pifagor.net | |||
17 | ||||
(le) | profiag.com | |||
(le) | agrifop.sk | |||
(le) | pifagor.kz | |||
(le) | pifagor.com | |||
(le) | apifrog.com | |||
(le) | pifagor.ru | |||
(le) | pifagor.net | |||
(le) | opigraf.com | |||
(le) | piograf.net | |||
(le) | fragopi.de | |||
(le) | pifagor.info | |||
(le) | pifagor.org | |||
(le) | agprofi.com | |||
(le) | pifagor.io | |||
(le) | pifagor.su | |||
(le) | opgrafi.com.ph | |||
(le) | pifrago.at |
AI analysis
The parent of intranet.pifagor.kz is pifagor.kz.
pifagor.kz is associated with a single IP address: 213.130.74.45.
IP numbers are shared between pifagor.kz and other host names, such as roman-empire.ru, cleaning-service.kz, agran.kz, jurguru.ru, and artglass.kz.
Three name servers, ns1.ps.kz, ns2.ps.kz, and ns3.ps.kz, are delegated to pifagor.kz.
The domain pifagor.kz shares name servers, at least partially, with other domains such as bcs.kz, medcentre.kz, cy.kz, jpg.kz, and bibliotekar.kz.
The name servers ns.ps.kz are frequently utilized in combination with these name servers.
ns1.ps.kz, 2a00:5da0:0:1::194, and 195.210.46.194 are associated with multiple IP numbers. Similarly, ns2.ps.kz, 2a00:5da0:1:1::172, and 195.210.46.172 have multiple IP numbers assigned to them. Additionally, ns3.ps.kz is linked to a single IP number, 31.210.174.104.
The handling of pifagor.kz is managed by these six mail servers: aspmx.l.google.com, 626ssi2njzexbiy2t3ehbybq25sqcu4am767kcmqfhx2463gfrtq.mx-verification.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com, and alt4.aspmx.l.google.com.
Other domains like sawkins.name, rfid4u.com, roussellsgarden.com, tabla.me, and appgump.com share some mail servers, at least partially, with pifagor.kz.
The mail servers aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com, and aspmx5.googlemail.com are commonly used in conjunction with these mail servers.
aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com, and alt4.aspmx.l.google.com each point to two IP numbers: 2a00:1450:400c:c1d::1a and 142.251.168.26, 2a00:1450:4013:c16::1a and 142.250.153.26, 2a00:1450:4025:c03::1a and 142.251.9.27, 2a00:1450:4025:401::1b and 142.250.27.27, 2a00:1450:4013:c16::1a and 142.250.153.27 respectively.