apiperf-bing-int.com - robtex.com

apiperf-bing-int.com

com

Same first word

DNS History

9 records (5 active, 4 former)

20162017201820192020202120222023202420252026NSns1-02.azure-dns.comns2-02.azure-dns.netns3-02.azure-dns.orgns4-02.azure-dns.infons1.msedge.netns2.msedge.netns3.msedge.netns4.msedge.netA131.253.13.102
NSns1-02.azure-dns.com2020-01-15 → 2026-07-14 · 3 obs
○ 2017-03-17 10:18:44
● 2020-01-15 04:57:44
● 2026-07-14 07:24:00
NSns1.msedge.net2015-05-30 → 2017-03-17 · 4 obs
● 2015-05-30 03:37:52
● 2017-03-17 10:18:44
○ 2020-01-15 04:57:44
○ 2026-07-14 07:24:00
NSns2-02.azure-dns.net2020-01-15 → 2026-07-14 · 3 obs
○ 2017-03-17 10:18:44
● 2020-01-15 04:57:44
● 2026-07-14 07:24:00
NSns2.msedge.net2015-05-30 → 2017-03-17 · 4 obs
● 2015-05-30 03:37:52
● 2017-03-17 10:18:44
○ 2020-01-15 04:57:44
○ 2026-07-14 07:24:00
NSns3-02.azure-dns.org2020-01-15 → 2026-07-14 · 3 obs
○ 2017-03-17 10:18:44
● 2020-01-15 04:57:44
● 2026-07-14 07:24:00
NSns3.msedge.net2015-05-30 → 2017-03-17 · 4 obs
● 2015-05-30 03:37:52
● 2017-03-17 10:18:44
○ 2020-01-15 04:57:44
○ 2026-07-14 07:24:00
NSns4-02.azure-dns.info2020-01-15 → 2026-07-14 · 3 obs
○ 2017-03-17 10:18:44
● 2020-01-15 04:57:44
● 2026-07-14 07:24:00
NSns4.msedge.net2015-05-30 → 2017-03-17 · 4 obs
● 2015-05-30 03:37:52
● 2017-03-17 10:18:44
○ 2020-01-15 04:57:44
○ 2026-07-14 07:24:00
A131.253.13.1022015-05-30 → 2026-07-14 · 2 obs
● 2015-05-30 03:37:52
● 2026-07-14 07:24:00

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
apiperf-bing-int.comns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info2 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 apiperf-bing-int.com (unsigned zone)

⏱️ Timing

Total: 424ms | Queries: -

📄 Records

TypeCountSample Data
A1131.253.13.102
NS4ns1-02.azure-dns.com, ns2-02.azure-dns.net...
SOA1ns1-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

apiperf-bing-int.com points to a single IP number: 131.253.13.102.

Additional host names — bing-int2.com, dev4-bing-int2.com, dev8-bing4-int.com and two others — share IP numbers with apiperf-bing-int.com.

Name Servers

apiperf-bing-int.com has four authoritative name servers: ns1-02.azure-dns.com, ns4-02.azure-dns.info, ns2-02.azure-dns.net and ns3-02.azure-dns.org.

There is at least partial name server overlap between apiperf-bing-int.com and other domains — msedge.tw, salesscreen.com, ccr.ca and two more among them.

These name servers tend to appear in combination with the name servers dns1.p05.nsone.net, dns2.p05.nsone.net, dns3.p05.nsone.net and dns4.p05.nsone.net.

All four hostnames — ns1-02.azure-dns.com, ns4-02.azure-dns.info, ns2-02.azure-dns.net and ns3-02.azure-dns.org — resolve to two IP numbers apiece: ns1-02.azure-dns.com to 13.107.236.2 and 2603:1061:0:700::2; ns4-02.azure-dns.info to 208.84.5.2 and 2620:1ec:bda:700::2; ns2-02.azure-dns.net to 150.171.21.2 and 2620:1ec:8ec:700::2; ns3-02.azure-dns.org to 204.14.183.2 and 2a01:111:4000:700::2.