bingfund.com - robtex.com
bingfund.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 20.70.246.20🇦🇺 Microsoft20.64.0.0/10 | ||||||
| A | 20.76.201.171🇳🇱 Microsoft20.64.0.0/10 | ||||||
| A | 20.112.250.133🇺🇸 Microsoft20.64.0.0/10 | ||||||
| A | 20.231.239.246🇺🇸 Microsoft20.192.0.0/10 | ||||||
| A | 20.236.44.162🇺🇸 Microsoft20.192.0.0/10 | ||||||
| NS | ns1-02.azure-dns.com ⭐ | ||||||
| A | 2603:1061:0:700::2🇺🇸 Microsoft2603:1000::/25 MICROSOFT | ||||||
| PTR | ns1-02.azure-dns.com | ||||||
| A | 13.107.236.2🇺🇸 Microsoft13.104.0.0/14 MICROSOFT | ||||||
| PTR | ns1-02.azure-dns.com | ||||||
| NS | ns2-02.azure-dns.net | ||||||
| A | 2620:1ec:8ec:700::2🇺🇸 Microsoft2620:1ec::/36 MICROSOFT | ||||||
| PTR | ns2-02.azure-dns.net | ||||||
| A | 150.171.21.2🇺🇸 Microsoft150.171.0.0/16 MICROSOFT | ||||||
| PTR | ns2-02.azure-dns.net | ||||||
| NS | ns3-02.azure-dns.org | ||||||
| A | 2a01:111:4000:700::2🇬🇧 Microsoft2a01:111:4000::/36 | ||||||
| PTR | ns3-02.azure-dns.org | ||||||
| A | 204.14.183.2🇺🇸 Microsoft204.14.180.0/22 | ||||||
| PTR | ns3-02.azure-dns.org | ||||||
| NS | ns4-02.azure-dns.info | ||||||
| A | 2620:1ec:bda:700::2🇺🇸 Microsoft2620:1ec::/36 MICROSOFT | ||||||
| PTR | ns4-02.azure-dns.info | ||||||
| A | 208.84.5.2🇺🇸 Microsoft208.84.0.0/21 MICROSOFT | ||||||
| PTR | ns4-02.azure-dns.info | ||||||
| SOA | ns1-02.azure-dns.comazuredns-hostmaster@microsoft.com serial=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=1771291435 | ||||||
Same first word
Similar names
DNS History
19 records (9 active, 10 former)
●NSns1-02.azure-dns.com2019-09-02 → 2026-03-22 · 3 obs
● 2019-09-02 06:06:18
● 2026-03-22 14:39:50
○NSns1.msft.net2015-07-18 → 2017-03-24 · 4 obs
● 2017-03-24 19:08:08
○ 2019-09-02 06:06:18
○ 2026-03-22 14:39:50
●NSns2-02.azure-dns.net2019-09-02 → 2026-03-22 · 3 obs
● 2019-09-02 06:06:18
● 2026-03-22 14:39:50
○NSns2.msft.net2015-07-18 → 2017-03-24 · 4 obs
● 2017-03-24 19:08:08
○ 2019-09-02 06:06:18
○ 2026-03-22 14:39:50
●NSns3-02.azure-dns.org2019-09-02 → 2026-03-22 · 3 obs
● 2019-09-02 06:06:18
● 2026-03-22 14:39:50
○NSns3.msft.net2015-07-18 → 2017-03-24 · 4 obs
● 2017-03-24 19:08:08
○ 2019-09-02 06:06:18
○ 2026-03-22 14:39:50
●NSns4-02.azure-dns.info2019-09-02 → 2026-03-22 · 3 obs
● 2019-09-02 06:06:18
● 2026-03-22 14:39:50
○NSns4.msft.net2015-07-18 → 2017-03-24 · 4 obs
● 2017-03-24 19:08:08
○ 2019-09-02 06:06:18
○ 2026-03-22 14:39:50
○A104.215.95.1872019-09-02 → 2019-10-21 · 5 obs
● 2019-09-02 06:06:18
● 2019-10-21 13:32:28
○ 2026-02-28 13:04:14
○ 2026-03-22 14:39:50
●A20.112.250.1332026-02-28 → 2026-03-22 · 3 obs
● 2026-02-28 13:04:14
● 2026-03-22 14:39:50
●A20.231.239.2462026-02-28 → 2026-03-22 · 3 obs
● 2026-02-28 13:04:14
● 2026-03-22 14:39:50
●A20.236.44.1622026-02-28 → 2026-03-22 · 3 obs
● 2026-02-28 13:04:14
● 2026-03-22 14:39:50
●A20.70.246.202026-02-28 → 2026-03-22 · 3 obs
● 2026-02-28 13:04:14
● 2026-03-22 14:39:50
●A20.76.201.1712026-02-28 → 2026-03-22 · 3 obs
● 2026-02-28 13:04:14
● 2026-03-22 14:39:50
○A40.84.199.2332017-03-24 → 2017-03-24 · 4 obs
● 2017-03-24 19:08:08
○ 2019-09-02 06:06:18
○ 2026-03-22 14:39:50
○A52.164.206.562019-09-02 → 2019-10-21 · 5 obs
● 2019-09-02 06:06:18
● 2019-10-21 13:32:28
○ 2026-02-28 13:04:14
○ 2026-03-22 14:39:50
○A52.178.167.1092017-03-24 → 2017-03-24 · 4 obs
● 2017-03-24 19:08:08
○ 2019-09-02 06:06:18
○ 2026-03-22 14:39:50
○A64.4.6.1002015-07-18 → 2016-05-10 · 4 obs
● 2016-05-10 14:18:34
○ 2017-03-24 19:08:08
○ 2026-03-22 14:39:50
○A65.55.39.102015-07-18 → 2016-05-10 · 4 obs
● 2016-05-10 14:18:34
○ 2017-03-24 19:08:08
○ 2026-03-22 14:39:50
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| bingfund.com | ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info | 2 records |
✅ Authoritative Response
Server: 208.84.5.2
NS records: ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for bingfund.com (unsigned zone)
⏱️ Timing
Total: 834ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 5 | 20.76.201.171, 20.112.250.133... |
| NS | 4 | ns1-02.azure-dns.com, ns2-02.azure-dns.net... |
| SOA | 1 | ns1-02.azure-dns.com azuredns-hostmaster |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1-02.azure-dns.com, ns1-02.azure-dns.com)
Analysis
IP Addresses
bingfund.com points to five IPs: 20.70.246.20, 20.76.201.171, 20.112.250.133, 20.231.239.246 and 20.236.44.162.
Other host names, for instance excel-china.com.cn, aominsider.org, imagine-windowslive.com, windowslivemail.se and reactorms.ca share IP numbers with bingfund.com.
Name Servers
bingfund.com is delegated to four name servers: ns1-02.azure-dns.com, ns4-02.azure-dns.info, ns2-02.azure-dns.net and ns3-02.azure-dns.org.
bingfund.com at least partially shares name servers with other domains, for instance ibope.com, phponwindows.ca, cloud.ains.net.au, humancampus.nl and educaedu.pe.
Host names with two IP numbers:
ns1-02.azure-dns.com points to: 2603:1061:0:700::2 and 13.107.236.2.
ns4-02.azure-dns.info points to: 2620:1ec:bda:700::2 and 208.84.5.2.
ns2-02.azure-dns.net points to: 2620:1ec:8ec:700::2 and 150.171.21.2.
ns3-02.azure-dns.org points to: 2a01:111:4000:700::2 and 204.14.183.2.