The Internet Backbone Search Engine Abongo
Enter an IP, Domain or Website. We'll tell you all about it.
Greetings from our Virginia spider! You may also use:   Montréal San FranciscoSão PauloLondonBarcelonaParisZurichFrankfurtStockholmMilanCape TownDubaiBahrainMumbaiSydneyJakartaSingaporeHong KongSeoulTokyo
RDNS Report on ns1.netnames.net
This RDNS Report on ns1.netnames.net was prepared on Tue, 10 Jun 2025 20:43:13 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.
NOTE: ns1.netnames.net resolves to 156.154.130.100 and 2610:a1:1022::100. 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
156.154.130.100 Copy
 ✅ ns.domainnetwork.se Copy
✅ ns.domainnetwork.se OK
ns.domainnetwork.se resolves to 156.154.130.100 as expected.
✅ ns.domainnetwork.se OK
ns.domainnetwork.se resolves to 2610:a1:1022::100 . This obviously does not match 156.154.130.100 but there is another record for ns.domainnetwork.se which matches.
2610:a1:1022::100 Copy
NOTE: Multiple PTR records set.
 ✅ ns.domainnetwork.se Copy
✅ ns1.netnames.net Copy
✅ ns3.netnames.net Copy
✅ pdns1.cscdns.net Copy
✅ ns5.netnames.net Copy
✅ indom30.indomco.fr Copy
✅ ns0.netnames.net Copy
✅ ns1.arcemus.com Copy
✅ dns1.cscdns.net Copy
✅ ns3.ascio.net Copy
✅ ns1.ascio.net Copy
✅ ns2.euro909.com Copy
✅ kandns06.digitalarchives.com Copy
✅ ns2.domainnetwork.se Copy
✅ indom10.indomco.com Copy
✅ ns1.euro909.com Copy
✅ indom130.indomco.org Copy
✅ spdns3.cscdns.net Copy
✅ sbdns3.cscdns.net Copy
✅ ns7.netnames.net Copy
✅ ns.domainnetwork.se OK
ns.domainnetwork.se resolves to 156.154.130.100 . This obviously does not match 2610:a1:1022::100 but there is another record for ns.domainnetwork.se which matches.
✅ ns.domainnetwork.se OK
ns.domainnetwork.se resolves to 2610:a1:1022::100 as expected.
✅ ns1.netnames.net OK
ns1.netnames.net resolves to 156.154.130.100 . This obviously does not match 2610:a1:1022::100 but there is another record for ns1.netnames.net which matches.
✅ ns1.netnames.net OK
ns1.netnames.net resolves to 2610:a1:1022::100 as expected.
✅ ns3.netnames.net OK
ns3.netnames.net resolves to 156.154.130.100 . This obviously does not match 2610:a1:1022::100 but there is another record for ns3.netnames.net which matches.
✅ ns3.netnames.net OK
ns3.netnames.net resolves to 2610:a1:1022::100 as expected.
✅ pdns1.cscdns.net OK
pdns1.cscdns.net resolves to 156.154.130.100 . This obviously does not match 2610:a1:1022::100 but there is another record for pdns1.cscdns.net which matches.
✅ pdns1.cscdns.net OK
pdns1.cscdns.net resolves to 2610:a1:1022::100 as expected.
✅ ns5.netnames.net OK
ns5.netnames.net resolves to 156.154.130.100 . This obviously does not match 2610:a1:1022::100 but there is another record for ns5.netnames.net which matches.
✅ ns5.netnames.net OK
ns5.netnames.net resolves to 2610:a1:1022::100 as expected.
✅ indom30.indomco.fr OK
indom30.indomco.fr resolves to 156.154.130.100 . This obviously does not match 2610:a1:1022::100 but there is another record for indom30.indomco.fr which matches.
✅ indom30.indomco.fr OK
indom30.indomco.fr resolves to 2610:a1:1022::100 as expected.
✅ ns0.netnames.net OK
ns0.netnames.net resolves to 156.154.130.100 . This obviously does not match 2610:a1:1022::100 but there is another record for ns0.netnames.net which matches.
✅ ns0.netnames.net OK
ns0.netnames.net resolves to 2610:a1:1022::100 as expected.
✅ ns1.arcemus.com OK
ns1.arcemus.com resolves to 156.154.130.100 . This obviously does not match 2610:a1:1022::100 but there is another record for ns1.arcemus.com which matches.
✅ ns1.arcemus.com OK
ns1.arcemus.com resolves to 2610:a1:1022::100 as expected.
✅ dns1.cscdns.net OK
dns1.cscdns.net resolves to 156.154.130.100 . This obviously does not match 2610:a1:1022::100 but there is another record for dns1.cscdns.net which matches.
✅ dns1.cscdns.net OK
dns1.cscdns.net resolves to 2610:a1:1022::100 as expected.
✅ ns3.ascio.net OK
ns3.ascio.net resolves to 156.154.130.100 . This obviously does not match 2610:a1:1022::100 but there is another record for ns3.ascio.net which matches.
✅ ns3.ascio.net OK
ns3.ascio.net resolves to 2610:a1:1022::100 as expected.
✅ ns1.ascio.net OK
ns1.ascio.net resolves to 156.154.130.100 . This obviously does not match 2610:a1:1022::100 but there is another record for ns1.ascio.net which matches.
✅ ns1.ascio.net OK
ns1.ascio.net resolves to 2610:a1:1022::100 as expected.
✅ ns2.euro909.com OK
ns2.euro909.com resolves to 156.154.130.100 . This obviously does not match 2610:a1:1022::100 but there is another record for ns2.euro909.com which matches.
✅ ns2.euro909.com OK
ns2.euro909.com resolves to 2610:a1:1022::100 as expected.
❌ kandns06.digitalarchives.com FAILED
kandns06.digitalarchives.com resolves to 209.112.114.33 which does not match 156.154.130.100 or 2610:a1:1022::100.
✅ ns2.domainnetwork.se OK
ns2.domainnetwork.se resolves to 156.154.130.100 . This obviously does not match 2610:a1:1022::100 but there is another record for ns2.domainnetwork.se which matches.
✅ ns2.domainnetwork.se OK
ns2.domainnetwork.se resolves to 2610:a1:1022::100 as expected.
✅ indom10.indomco.com OK
indom10.indomco.com resolves to 156.154.130.100 . This obviously does not match 2610:a1:1022::100 but there is another record for indom10.indomco.com which matches.
✅ indom10.indomco.com OK
indom10.indomco.com resolves to 2610:a1:1022::100 as expected.
✅ ns1.euro909.com OK
ns1.euro909.com resolves to 156.154.130.100 . This obviously does not match 2610:a1:1022::100 but there is another record for ns1.euro909.com which matches.
✅ ns1.euro909.com OK
ns1.euro909.com resolves to 2610:a1:1022::100 as expected.
✅ indom130.indomco.org OK
indom130.indomco.org resolves to 156.154.130.100 . This obviously does not match 2610:a1:1022::100 but there is another record for indom130.indomco.org which matches.
✅ indom130.indomco.org OK
indom130.indomco.org resolves to 2610:a1:1022::100 as expected.
✅ spdns3.cscdns.net OK
spdns3.cscdns.net resolves to 156.154.130.100 . This obviously does not match 2610:a1:1022::100 but there is another record for spdns3.cscdns.net which matches.
✅ spdns3.cscdns.net OK
spdns3.cscdns.net resolves to 2610:a1:1022::100 as expected.
✅ sbdns3.cscdns.net OK
sbdns3.cscdns.net resolves to 156.154.130.100 . This obviously does not match 2610:a1:1022::100 but there is another record for sbdns3.cscdns.net which matches.
✅ sbdns3.cscdns.net OK
sbdns3.cscdns.net resolves to 2610:a1:1022::100 as expected.
✅ ns7.netnames.net OK
ns7.netnames.net resolves to 156.154.130.100 . This obviously does not match 2610:a1:1022::100 but there is another record for ns7.netnames.net which matches.
✅ ns7.netnames.net OK
ns7.netnames.net resolves to 2610:a1:1022::100 as expected.