bingoconnect.com - dns.ninja
bingoconnect.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 13.248.213.45🇺🇸 Amazon13.248.208.0/20 | ||||||
| PTR | a67c48129651a0940.awsglobalaccelerator.com | ||||||
| A | 76.223.67.189🇺🇸 Amazon76.223.64.0/20 | ||||||
| NS | ns59.domaincontrol.com ⭐ | ||||||
| A | 2603:5:2143::1f🇺🇸 GODADDY-DNS2603:5:2140::/44 | ||||||
| PTR | mns01.domaincontrol.com | ||||||
| A | 97.74.100.31🇺🇸 GODADDY-DNS97.74.100.0/23 | ||||||
| PTR | ns59.domaincontrol.com | ||||||
| NS | ns60.domaincontrol.com | ||||||
| A | 2603:5:2243::1f🇺🇸 GODADDY-DNS2603:5:2240::/44 | ||||||
| PTR | mns02.domaincontrol.com | ||||||
| A | 173.201.68.31🇺🇸 GODADDY-DNS173.201.68.0/23 | ||||||
| PTR | ns60.domaincontrol.com | ||||||
| SOA | ns59.domaincontrol.comdns@jomax.net 2026-07-03 #1 | ||||||
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1785277132 | ||||||
Same first word
bingoconnect.com |
bingoconnect.uk |
Similar names
DNS History
16 records (4 active, 12 former)
○NSbuy.internettraffic.com2015-08-10 → 2016-02-28 · 4 obs
● 2015-08-10 14:23:20
● 2016-02-28 06:59:32
○ 2017-02-19 06:50:00
○ 2026-07-28 22:29:34
● 2016-02-28 06:59:32
○ 2017-02-19 06:50:00
○ 2026-07-28 22:29:34
○NSns1.uniregistrymarket.link2017-02-19 → 2017-02-19 · 4 obs
○ 2016-02-28 06:59:32
● 2017-02-19 06:50:00
○ 2026-03-19 21:56:24
○ 2026-07-28 22:29:34
● 2017-02-19 06:50:00
○ 2026-03-19 21:56:24
○ 2026-07-28 22:29:34
○NSns2.uniregistrymarket.link2017-02-19 → 2017-02-19 · 4 obs
○ 2016-02-28 06:59:32
● 2017-02-19 06:50:00
○ 2026-03-19 21:56:24
○ 2026-07-28 22:29:34
● 2017-02-19 06:50:00
○ 2026-03-19 21:56:24
○ 2026-07-28 22:29:34
○NSns3.afternic.com2026-03-19 → 2026-05-20 · 5 obs
○ 2017-02-19 06:50:00
● 2026-03-19 21:56:24
● 2026-05-20 23:17:44
○ 2026-07-03 17:18:40
○ 2026-07-28 22:29:34
● 2026-03-19 21:56:24
● 2026-05-20 23:17:44
○ 2026-07-03 17:18:40
○ 2026-07-28 22:29:34
○NSns4.afternic.com2026-03-19 → 2026-05-20 · 5 obs
○ 2017-02-19 06:50:00
● 2026-03-19 21:56:24
● 2026-05-20 23:17:44
○ 2026-07-03 17:18:40
○ 2026-07-28 22:29:34
● 2026-03-19 21:56:24
● 2026-05-20 23:17:44
○ 2026-07-03 17:18:40
○ 2026-07-28 22:29:34
●NSns59.domaincontrol.com2026-07-03 → 2026-07-28 · 3 obs
○ 2026-05-20 23:17:44
● 2026-07-03 17:18:40
● 2026-07-28 22:29:34
● 2026-07-03 17:18:40
● 2026-07-28 22:29:34
●NSns60.domaincontrol.com2026-07-03 → 2026-07-28 · 3 obs
○ 2026-05-20 23:17:44
● 2026-07-03 17:18:40
● 2026-07-28 22:29:34
● 2026-07-03 17:18:40
● 2026-07-28 22:29:34
○NSsell.internettraffic.com2015-08-10 → 2016-02-28 · 4 obs
● 2015-08-10 14:23:20
● 2016-02-28 06:59:32
○ 2017-02-19 06:50:00
○ 2026-07-28 22:29:34
● 2016-02-28 06:59:32
○ 2017-02-19 06:50:00
○ 2026-07-28 22:29:34
○NSverification-frsgyqgb387khmr9jzuunx.ns101.verify.hn2026-03-19 → 2026-05-20 · 5 obs
○ 2017-02-19 06:50:00
● 2026-03-19 21:56:24
● 2026-05-20 23:17:44
○ 2026-07-03 17:18:40
○ 2026-07-28 22:29:34
● 2026-03-19 21:56:24
● 2026-05-20 23:17:44
○ 2026-07-03 17:18:40
○ 2026-07-28 22:29:34
○A13.248.169.482026-03-19 → 2026-05-20 · 5 obs
○ 2017-02-19 06:50:00
● 2026-03-19 21:56:24
● 2026-05-20 23:17:44
○ 2026-07-03 17:18:40
○ 2026-07-28 22:29:34
● 2026-03-19 21:56:24
● 2026-05-20 23:17:44
○ 2026-07-03 17:18:40
○ 2026-07-28 22:29:34
●A13.248.213.452026-07-03 → 2026-07-28 · 3 obs
○ 2026-05-20 23:17:44
● 2026-07-03 17:18:40
● 2026-07-28 22:29:34
● 2026-07-03 17:18:40
● 2026-07-28 22:29:34
○A69.172.201.1532017-02-19 → 2017-02-19 · 4 obs
○ 2016-07-10 22:11:26
● 2017-02-19 06:50:00
○ 2026-03-19 21:56:24
○ 2026-07-28 22:29:34
● 2017-02-19 06:50:00
○ 2026-03-19 21:56:24
○ 2026-07-28 22:29:34
○A69.172.201.2082015-08-10 → 2016-02-28 · 4 obs
● 2015-08-10 14:23:20
● 2016-02-28 06:59:32
○ 2016-07-10 22:11:26
○ 2026-07-28 22:29:34
● 2016-02-28 06:59:32
○ 2016-07-10 22:11:26
○ 2026-07-28 22:29:34
○A69.64.147.2422016-07-10 → 2016-07-10 · 4 obs
○ 2016-02-28 06:59:32
● 2016-07-10 22:11:26
○ 2017-02-19 06:50:00
○ 2026-07-28 22:29:34
● 2016-07-10 22:11:26
○ 2017-02-19 06:50:00
○ 2026-07-28 22:29:34
○A76.223.54.1462026-03-19 → 2026-05-20 · 5 obs
○ 2017-02-19 06:50:00
● 2026-03-19 21:56:24
● 2026-05-20 23:17:44
○ 2026-07-03 17:18:40
○ 2026-07-28 22:29:34
● 2026-03-19 21:56:24
● 2026-05-20 23:17:44
○ 2026-07-03 17:18:40
○ 2026-07-28 22:29:34
●A76.223.67.1892026-07-03 → 2026-07-28 · 3 obs
○ 2026-05-20 23:17:44
● 2026-07-03 17:18:40
● 2026-07-28 22:29:34
● 2026-07-03 17:18:40
● 2026-07-28 22:29:34
🔍 DNS Trace
Analysis
IP Addresses
bingoconnect.com points to the IP addresses 13.248.213.45 and 76.223.67.189
Additional host names — 34000603oxhxjzt560.top, mta130.surveydownlinemail.com, www.gujaratnrecoke.com and two others — share IP numbers with bingoconnect.com.
Name Servers
bingoconnect.com has two authoritative name servers — ns59.domaincontrol.com and ns60.domaincontrol.com.
bingoconnect.com shares its name server setup with other domains, including pacificgrovedesign.com, afxlicensing.com, minvites.ca and two others.
Both ns59.domaincontrol.com and ns60.domaincontrol.com have two IP addresses each. ns59.domaincontrol.com resolves to 97.74.100.31 and 2603:5:2143::1f; ns60.domaincontrol.com resolves to 173.201.68.31 and 2603:5:2243::1f.