The Internet Backbone Search Engine Abongo
Enter an IP, Domain or Website. We'll tell you all about it.
Hi from our Montréal spider! You may also use:   San FranciscoVirginiaSão PauloLondonBarcelonaParisZurichFrankfurtStockholmMilanCape TownDubaiBahrainMumbaiSydneyJakartaSingaporeHong KongSeoulTokyo
RDNS Report on b23.verisigndns.com
This RDNS Report on b23.verisigndns.com was prepared on Tue, 23 Sep 2025 19:31:02 GMT by the Montréal 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: b23.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.
 ✅ b21.verisigndns.com Copy
✅ b23.verisigndns.com Copy
✅ b22.verisigndns.com Copy
✅ b2.verisigndns.com Copy
✅ 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.
✅ 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.
✅ 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.
❌ 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
 ✅ dns1.registrar-servers.com Copy
❌ 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.