The Internet Backbone Search Engine Abongo
Enter an IP, Domain or Website. We'll tell you all about it.
Nǐ hǎo from our Hong Kong spider! You may also use:   Montréal San FranciscoVirginiaSão PauloLondonBarcelonaParisZurichFrankfurtStockholmMilanCape TownDubaiBahrainMumbaiSydneyJakartaSingaporeSeoulTokyo
RDNS Report on b21.verisigndns.com
This RDNS Report on b21.verisigndns.com was prepared on Tue, 10 Jun 2025 19:46:46 GMT by the Hong Kong 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.
NOTE: b21.verisigndns.com resolves to 216.87.150.33 and 2620:74:19::33. RDNS records for each of those IP addresses are shown below.
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
216.87.150.33 Copy
NOTE: Multiple PTR records set.
 ✅ b22.verisigndns.com Copy
✅ b23.verisigndns.com Copy
✅ b21.verisigndns.com Copy
✅ b2.verisigndns.com Copy
✅ b22.verisigndns.com OK
b22.verisigndns.com resolves to 216.87.150.33 as expected.
✅ b22.verisigndns.com OK
b22.verisigndns.com resolves to 2620:74:19::33 . This obviously does not match 216.87.150.33 but there is another record for b22.verisigndns.com which matches.
✅ b23.verisigndns.com OK
b23.verisigndns.com resolves to 216.87.150.33 as expected.
✅ b23.verisigndns.com OK
b23.verisigndns.com resolves to 2620:74:19::33 . This obviously does not match 216.87.150.33 but there is another record for b23.verisigndns.com which matches.
✅ b21.verisigndns.com OK
b21.verisigndns.com resolves to 216.87.150.33 as expected.
✅ b21.verisigndns.com OK
b21.verisigndns.com resolves to 2620:74:19::33 . This obviously does not match 216.87.150.33 but there is another record for b21.verisigndns.com which matches.
❌ b2.verisigndns.com FAILED
b2.verisigndns.com resolves to 209.112.114.33 which does not match 216.87.150.33 or 2620:74:19::33.
✅ b2.verisigndns.com OK
b2.verisigndns.com resolves to 2620:74:19::33 . This obviously does not match 216.87.150.33 but there is another record for b2.verisigndns.com which matches.
2620:74:19::33 Copy
NOTE: Multiple PTR records set.
 ✅ ns3.netnames.net Copy
✅ ns1.netnames.net Copy
✅ pdns1.cscdns.net Copy
✅ a21.verisigndns.com Copy
✅ b21.verisigndns.com Copy
✅ a23.verisigndns.com Copy
✅ a22.verisigndns.com Copy
✅ b23.verisigndns.com Copy
✅ b22.verisigndns.com Copy
✅ ns5.netnames.net Copy
✅ pdns1.registrar-servers.com Copy
✅ k4.nstld.com Copy
✅ f4.nstld.com Copy
✅ indom30.indomco.fr Copy
✅ ns0.netnames.net Copy
✅ b2.verisigndns.com Copy
✅ a2.verisigndns.com Copy
✅ ns2.webipdns.com.au Copy
✅ dns1.cscdns.net Copy
✅ ns1.ascio.net Copy
✅ ns3.ascio.net Copy
✅ dns1.registrar-servers.com Copy
✅ indom10.indomco.com Copy
✅ indom130.indomco.org Copy
✅ dns1.namecheaphosting.com Copy
✅ ns7.netnames.net Copy
❌ ns3.netnames.net FAILED
ns3.netnames.net resolves to 156.154.130.100 which does not match 216.87.150.33 or 2620:74:19::33.
❌ ns3.netnames.net FAILED
ns3.netnames.net resolves to 2610:a1:1022::100 which does not match 216.87.150.33 or 2620:74:19::33.
❌ ns1.netnames.net FAILED
ns1.netnames.net resolves to 156.154.130.100 which does not match 216.87.150.33 or 2620:74:19::33.
❌ ns1.netnames.net FAILED
ns1.netnames.net resolves to 2610:a1:1022::100 which does not match 216.87.150.33 or 2620:74:19::33.
❌ pdns1.cscdns.net FAILED
pdns1.cscdns.net resolves to 156.154.130.100 which does not match 216.87.150.33 or 2620:74:19::33.
❌ pdns1.cscdns.net FAILED
pdns1.cscdns.net resolves to 2610:a1:1022::100 which does not match 216.87.150.33 or 2620:74:19::33.
❌ a21.verisigndns.com FAILED
a21.verisigndns.com resolves to 209.112.114.33 which does not match 216.87.150.33 or 2620:74:19::33.
✅ a21.verisigndns.com OK
a21.verisigndns.com resolves to 2620:74:19::33 as expected.
✅ b21.verisigndns.com OK
b21.verisigndns.com resolves to 216.87.150.33 . This obviously does not match 2620:74:19::33 but there is another record for b21.verisigndns.com which matches.
✅ b21.verisigndns.com OK
b21.verisigndns.com resolves to 2620:74:19::33 as expected.
❌ a23.verisigndns.com FAILED
a23.verisigndns.com resolves to 209.112.114.33 which does not match 216.87.150.33 or 2620:74:19::33.
✅ a23.verisigndns.com OK
a23.verisigndns.com resolves to 2620:74:19::33 as expected.
❌ a22.verisigndns.com FAILED
a22.verisigndns.com resolves to 209.112.114.33 which does not match 216.87.150.33 or 2620:74:19::33.
✅ a22.verisigndns.com OK
a22.verisigndns.com resolves to 2620:74:19::33 as expected.
✅ b23.verisigndns.com OK
b23.verisigndns.com resolves to 216.87.150.33 . This obviously does not match 2620:74:19::33 but there is another record for b23.verisigndns.com which matches.
✅ b23.verisigndns.com OK
b23.verisigndns.com resolves to 2620:74:19::33 as expected.
✅ b22.verisigndns.com OK
b22.verisigndns.com resolves to 216.87.150.33 . This obviously does not match 2620:74:19::33 but there is another record for b22.verisigndns.com which matches.
✅ b22.verisigndns.com OK
b22.verisigndns.com resolves to 2620:74:19::33 as expected.
❌ ns5.netnames.net FAILED
ns5.netnames.net resolves to 156.154.130.100 which does not match 216.87.150.33 or 2620:74:19::33.
❌ ns5.netnames.net FAILED
ns5.netnames.net resolves to 2610:a1:1022::100 which does not match 216.87.150.33 or 2620:74:19::33.
❌ pdns1.registrar-servers.com FAILED
pdns1.registrar-servers.com resolves to 156.154.132.100 which does not match 216.87.150.33 or 2620:74:19::33.
❌ pdns1.registrar-servers.com FAILED
pdns1.registrar-servers.com resolves to 2610:a1:1024::100 which does not match 216.87.150.33 or 2620:74:19::33.
❌ k4.nstld.com FAILED
k4.nstld.com resolves to 43.247.170.1 which does not match 216.87.150.33 or 2620:74:19::33.
❌ k4.nstld.com FAILED
k4.nstld.com resolves to 2600:180c:3001::1 which does not match 216.87.150.33 or 2620:74:19::33.
❌ f4.nstld.com FAILED
f4.nstld.com resolves to 46.31.236.1 which does not match 216.87.150.33 or 2620:74:19::33.
❌ f4.nstld.com FAILED
f4.nstld.com resolves to 2600:180b:2001::1 which does not match 216.87.150.33 or 2620:74:19::33.
❌ indom30.indomco.fr FAILED
indom30.indomco.fr resolves to 156.154.130.100 which does not match 216.87.150.33 or 2620:74:19::33.
❌ indom30.indomco.fr FAILED
indom30.indomco.fr resolves to 2610:a1:1022::100 which does not match 216.87.150.33 or 2620:74:19::33.
❌ ns0.netnames.net FAILED
ns0.netnames.net resolves to 156.154.130.100 which does not match 216.87.150.33 or 2620:74:19::33.
❌ ns0.netnames.net FAILED
ns0.netnames.net resolves to 2610:a1:1022::100 which does not match 216.87.150.33 or 2620:74:19::33.
❌ b2.verisigndns.com FAILED
b2.verisigndns.com resolves to 209.112.114.33 which does not match 216.87.150.33 or 2620:74:19::33.
✅ b2.verisigndns.com OK
b2.verisigndns.com resolves to 2620:74:19::33 as expected.
❌ a2.verisigndns.com FAILED
a2.verisigndns.com resolves to 46.31.236.1 which does not match 216.87.150.33 or 2620:74:19::33.
❌ a2.verisigndns.com FAILED
a2.verisigndns.com resolves to 2600:180b:2001::1 which does not match 216.87.150.33 or 2620:74:19::33.
❌ ns2.webipdns.com.au FAILED
ns2.webipdns.com.au resolves to 204.74.111.1 which does not match 216.87.150.33 or 2620:74:19::33.
❌ ns2.webipdns.com.au FAILED
ns2.webipdns.com.au resolves to 2001:502:4612::201 which does not match 216.87.150.33 or 2620:74:19::33.
❌ dns1.cscdns.net FAILED
dns1.cscdns.net resolves to 156.154.130.100 which does not match 216.87.150.33 or 2620:74:19::33.
❌ dns1.cscdns.net FAILED
dns1.cscdns.net resolves to 2610:a1:1022::100 which does not match 216.87.150.33 or 2620:74:19::33.
❌ ns1.ascio.net FAILED
ns1.ascio.net resolves to 156.154.130.100 which does not match 216.87.150.33 or 2620:74:19::33.
❌ ns1.ascio.net FAILED
ns1.ascio.net resolves to 2610:a1:1022::100 which does not match 216.87.150.33 or 2620:74:19::33.
❌ ns3.ascio.net FAILED
ns3.ascio.net resolves to 156.154.130.100 which does not match 216.87.150.33 or 2620:74:19::33.
❌ ns3.ascio.net FAILED
ns3.ascio.net resolves to 2610:a1:1022::100 which does not match 216.87.150.33 or 2620:74:19::33.
❌ dns1.registrar-servers.com FAILED
dns1.registrar-servers.com resolves to 156.154.132.200 which does not match 216.87.150.33 or 2620:74:19::33.
❌ dns1.registrar-servers.com FAILED
dns1.registrar-servers.com resolves to 2610:a1:1024::200 which does not match 216.87.150.33 or 2620:74:19::33.
❌ indom10.indomco.com FAILED
indom10.indomco.com resolves to 156.154.130.100 which does not match 216.87.150.33 or 2620:74:19::33.
❌ indom10.indomco.com FAILED
indom10.indomco.com resolves to 2610:a1:1022::100 which does not match 216.87.150.33 or 2620:74:19::33.
❌ indom130.indomco.org FAILED
indom130.indomco.org resolves to 156.154.130.100 which does not match 216.87.150.33 or 2620:74:19::33.
❌ indom130.indomco.org FAILED
indom130.indomco.org resolves to 2610:a1:1022::100 which does not match 216.87.150.33 or 2620:74:19::33.
❌ dns1.namecheaphosting.com FAILED
dns1.namecheaphosting.com resolves to 156.154.132.200 which does not match 216.87.150.33 or 2620:74:19::33.
❌ dns1.namecheaphosting.com FAILED
dns1.namecheaphosting.com resolves to 2610:a1:1024::200 which does not match 216.87.150.33 or 2620:74:19::33.
❌ ns7.netnames.net FAILED
ns7.netnames.net resolves to 156.154.130.100 which does not match 216.87.150.33 or 2620:74:19::33.
❌ ns7.netnames.net FAILED
ns7.netnames.net resolves to 2610:a1:1022::100 which does not match 216.87.150.33 or 2620:74:19::33.