IPLIST.NET - 389tcp.org
Search for IP or hostnames:
389tcp.org checked at 2025-09-15T16:42:01.630Z 828ms 105/105/105 100% R:25
389tcp.org
MX | mx1.redhat.com | ||||||
A | 52.25.184.255🇺🇸 Amazon | ||||||
PTR | ec2-52-25-184-255.us-west-2.compute.amazonaws.com | ||||||
MX | mx2.redhat.com | ||||||
A | 52.25.184.255🇺🇸 Amazon | ||||||
PTR | ec2-52-25-184-255.us-west-2.compute.amazonaws.com | ||||||
NS | ns01.fedoraproject.org | ||||||
A | 2620:52:6:1121:bead:cafe:feed:fed3 🇺🇸 REDHAT-IAD2Hosted | ||||||
A | 38.145.32.13🇺🇸 REDHAT-IAD2Hosted | ||||||
PTR | ns01.fedoraproject.org | ||||||
NS | ns02.fedoraproject.org | ||||||
A | 2606:f640:6000:651::11 🇺🇸 UNC-CH | ||||||
A | 152.2.23.107🇺🇸 UNC-CH | ||||||
NS | ns03.fedoraproject.org | ||||||
A | 2620:52:6:1121:bead:cafe:feed:fed4 🇺🇸 REDHAT-IAD2Hosted | ||||||
A | 38.145.32.14🇺🇸 REDHAT-IAD2Hosted | ||||||
PTR | ns02.fedoraproject.org | ||||||
NS | ns05.fedoraproject.org | ||||||
A | 2001:4178:2:1269:dead:beef:cafe:fed5 🇩🇪 InterNetX | ||||||
A | 85.236.55.10🇩🇪 InterNetX | ||||||
PTR | ns05.fedoraproject.org | ||||||
A | 38.145.32.20🇺🇸 REDHAT-IAD2Hosted | ||||||
PTR | proxy01.fedoraproject.org | ||||||
A | 38.145.32.21🇺🇸 REDHAT-IAD2Hosted | ||||||
PTR | proxy10.fedoraproject.org |
org
NS | a0.org.afilias-nst.info | ||||||
NS | a2.org.afilias-nst.info | ||||||
NS | c0.org.afilias-nst.info | ||||||
NS | b0.org.afilias-nst.org | ||||||
NS | b2.org.afilias-nst.org | ||||||
NS | d0.org.afilias-nst.org |
Starts with same word
389tcp.org |
Starts similarily
389tcp.org |
AI analysis
389tcp.org
points to two IP numbers: 38.145.32.20 and 38.145.32.21.
IP numbers are shared by 389tcp.org
with other host names like release-monitoring.org
, smolts.org
, cloud.fedoraproject.org
, lists.fedoraproject.org
, and kojipkgs.fedoraproject.org
.
Four name servers, ns01.fedoraproject.org
, ns02.fedoraproject.org
, ns03.fedoraproject.org
, and ns05.fedoraproject.org
, are responsible for the delegation of 389tcp.org
.
The domain 389tcp.org
shares its name servers at least partially with other domains such as fedp.org
, fedoralinux.org
, release-monitoring.org
, fedoraproject.info
, and fedoraproject.my
.
The name servers ns-iad01.fedoraproject.org
and ns-iad02.fedoraproject.org
are commonly used in conjunction with these name servers.
ns01.fedoraproject.org
, 2620:52:6:1121:bead:cafe:feed:fed3, and 38.145.32.13 are associated together.
ns02.fedoraproject.org
, 2606:f640:6000:651::11, and 152.2.23.107 are linked.
ns03.fedoraproject.org
, 2620:52:6:1121:bead:cafe:feed:fed4, and 38.145.32.14 are connected.
ns05.fedoraproject.org
, 2001:4178:2:1269:dead:beef:cafe:fed5, and 85.236.55.10 are paired.
The handling of 389tcp.org
is managed by two mail servers, namely mx1.redhat.com
and mx2.redhat.com
.
Just like the domains opensource.com
, aerogear.org
, quarkus.io
, fedora.im
, and fusesource.com
, 389tcp.org
also has the same mail server setup.
Some mail servers are shared, at least partially, by 389tcp.org
with other domains like redhathigh.com
, apacheweek.com
, openlmi.org
, ansible.ai
, and xdp-project.com
.
IP number 52.25.184.255 is pointed to by both mx1.redhat.com
and mx2.redhat.com
.