Greetings from our Virginia spider! You may also use:   Montréal San FranciscoSão PauloLondonBarcelonaParisZurichFrankfurtStockholmMilanCape TownDubaiBahrainMumbaiSydneyJakartaSingaporeHong KongSeoulTokyo
RDNS Report on 209.112.114.33
This RDNS Report on 209.112.114.33 was prepared on Tue, 10 Jun 2025 21:57:45 GMT by the Virginia spider on abongo.com. We welcome and value feedback and bug reports. This report is presented with no guarantees or warranties of any kind, expressed or implied, including any warranty of merchantability or fitness for a particular purpose.
Abongo is sponsored by Dymergent, the leader in Canadian research management and standards compliance. Contact Dymergent today to learn more about grant opportunities.
IP RDNS PTR Forward DNS Matches PTR
209.112.114.33 Copy
NOTE: Multiple PTR records set.
ns3.netnames.net Copy
ns1.netnames.net Copy
pdns1.cscdns.net Copy
a21.verisigndns.com Copy
a23.verisigndns.com Copy
a22.verisigndns.com Copy
ns5.netnames.net Copy
k4.nstld.com Copy
l4.nstld.com Copy
g4.nstld.com Copy
f4.nstld.com Copy
indom30.indomco.fr Copy
ns0.netnames.net Copy
a2.verisigndns.com Copy
ns2.webipdns.com.au Copy
dns1.cscdns.net Copy
ns3.ascio.net Copy
ns1.ascio.net Copy
ns2.euro909.com Copy
ns2.domainnetwork.se Copy
indom10.indomco.com Copy
ns2.dnsvisa.com Copy
indom130.indomco.org Copy
ns7.netnames.net Copy
ns3.netnames.net FAILED
ns3.netnames.net resolves to 156.154.130.100 which does not match 209.112.114.33.
ns3.netnames.net FAILED
ns3.netnames.net resolves to 2610:a1:1022::100 which does not match 209.112.114.33.
ns1.netnames.net FAILED
ns1.netnames.net resolves to 156.154.130.100 which does not match 209.112.114.33.
ns1.netnames.net FAILED
ns1.netnames.net resolves to 2610:a1:1022::100 which does not match 209.112.114.33.
pdns1.cscdns.net FAILED
pdns1.cscdns.net resolves to 156.154.130.100 which does not match 209.112.114.33.
pdns1.cscdns.net FAILED
pdns1.cscdns.net resolves to 2610:a1:1022::100 which does not match 209.112.114.33.
a21.verisigndns.com FAILED
a21.verisigndns.com resolves to 2620:74:19::33 which does not match 209.112.114.33.
a23.verisigndns.com FAILED
a23.verisigndns.com resolves to 2620:74:19::33 which does not match 209.112.114.33.
a22.verisigndns.com FAILED
a22.verisigndns.com resolves to 2620:74:19::33 which does not match 209.112.114.33.
ns5.netnames.net FAILED
ns5.netnames.net resolves to 156.154.130.100 which does not match 209.112.114.33.
ns5.netnames.net FAILED
ns5.netnames.net resolves to 2610:a1:1022::100 which does not match 209.112.114.33.
k4.nstld.com FAILED
k4.nstld.com resolves to 43.247.170.1 which does not match 209.112.114.33.
k4.nstld.com FAILED
k4.nstld.com resolves to 2600:180c:3001::1 which does not match 209.112.114.33.
l4.nstld.com FAILED
l4.nstld.com resolves to 96.45.80.1 which does not match 209.112.114.33.
l4.nstld.com FAILED
l4.nstld.com resolves to 2600:180a:1001::1 which does not match 209.112.114.33.
g4.nstld.com FAILED
g4.nstld.com resolves to 43.247.170.1 which does not match 209.112.114.33.
g4.nstld.com FAILED
g4.nstld.com resolves to 2600:180c:3001::1 which does not match 209.112.114.33.
f4.nstld.com FAILED
f4.nstld.com resolves to 46.31.236.1 which does not match 209.112.114.33.
f4.nstld.com FAILED
f4.nstld.com resolves to 2600:180b:2001::1 which does not match 209.112.114.33.
indom30.indomco.fr FAILED
indom30.indomco.fr resolves to 156.154.130.100 which does not match 209.112.114.33.
indom30.indomco.fr FAILED
indom30.indomco.fr resolves to 2610:a1:1022::100 which does not match 209.112.114.33.
ns0.netnames.net FAILED
ns0.netnames.net resolves to 156.154.130.100 which does not match 209.112.114.33.
ns0.netnames.net FAILED
ns0.netnames.net resolves to 2610:a1:1022::100 which does not match 209.112.114.33.
a2.verisigndns.com FAILED
a2.verisigndns.com resolves to 46.31.236.1 which does not match 209.112.114.33.
a2.verisigndns.com FAILED
a2.verisigndns.com resolves to 2600:180b:2001::1 which does not match 209.112.114.33.
ns2.webipdns.com.au FAILED
ns2.webipdns.com.au resolves to 204.74.111.1 which does not match 209.112.114.33.
ns2.webipdns.com.au FAILED
ns2.webipdns.com.au resolves to 2001:502:4612::201 which does not match 209.112.114.33.
dns1.cscdns.net FAILED
dns1.cscdns.net resolves to 156.154.130.100 which does not match 209.112.114.33.
dns1.cscdns.net FAILED
dns1.cscdns.net resolves to 2610:a1:1022::100 which does not match 209.112.114.33.
ns3.ascio.net FAILED
ns3.ascio.net resolves to 156.154.130.100 which does not match 209.112.114.33.
ns3.ascio.net FAILED
ns3.ascio.net resolves to 2610:a1:1022::100 which does not match 209.112.114.33.
ns1.ascio.net FAILED
ns1.ascio.net resolves to 156.154.130.100 which does not match 209.112.114.33.
ns1.ascio.net FAILED
ns1.ascio.net resolves to 2610:a1:1022::100 which does not match 209.112.114.33.
ns2.euro909.com FAILED
ns2.euro909.com resolves to 156.154.130.100 which does not match 209.112.114.33.
ns2.euro909.com FAILED
ns2.euro909.com resolves to 2610:a1:1022::100 which does not match 209.112.114.33.
ns2.domainnetwork.se FAILED
ns2.domainnetwork.se resolves to 156.154.130.100 which does not match 209.112.114.33.
ns2.domainnetwork.se FAILED
ns2.domainnetwork.se resolves to 2610:a1:1022::100 which does not match 209.112.114.33.
indom10.indomco.com FAILED
indom10.indomco.com resolves to 156.154.130.100 which does not match 209.112.114.33.
indom10.indomco.com FAILED
indom10.indomco.com resolves to 2610:a1:1022::100 which does not match 209.112.114.33.
ns2.dnsvisa.com FAILED
ns2.dnsvisa.com resolves to 162.159.8.235 which does not match 209.112.114.33.
ns2.dnsvisa.com FAILED
ns2.dnsvisa.com resolves to 2400:cb00:2049:1::a29f:8eb which does not match 209.112.114.33.
indom130.indomco.org FAILED
indom130.indomco.org resolves to 156.154.130.100 which does not match 209.112.114.33.
indom130.indomco.org FAILED
indom130.indomco.org resolves to 2610:a1:1022::100 which does not match 209.112.114.33.
ns7.netnames.net FAILED
ns7.netnames.net resolves to 156.154.130.100 which does not match 209.112.114.33.
ns7.netnames.net FAILED
ns7.netnames.net resolves to 2610:a1:1022::100 which does not match 209.112.114.33.