DNS lookup


Query type:
 ANY  A  AAAA  MX  NS  SOA  TXT  SRV

Nameserver(s) to query:
If no nameserver is provided, authoritative server of domain is queried. Separate multiple nameservers useing space. Preselect google, cloudflare or openDNS.

A, AAAA, MX and TXT records of 'bing.com'

dns2.p09.nsone.net is refusing ANY-requests

RFC 8482 has been implemeneted by several DNS-servers in order to minimize DNS responses. They will deny responing to ANY-lookups.

The tool has modified the lookup in order to get useable answers for you.

Try A-records Try AAAA-records Try MX-records Try TXT-records

Answers

Records retrived from dns2.p09.nsone.net in 112ms
bing.com
A
13.107.21.200
bing.com
A
204.79.197.200
bing.com
AAAA
2620:1ec:c11::200
bing.com
MX
bing-com.mail.protection.outlook.com
Preference: 10
bing.com
TXT
facebook-domain-verification=09yg8uzcfnqnlqekzsbwjxyy8rdck7
bing.com
TXT
google-site-verification=OkRY8R261shK5B8uEwvsFZp9nQ2gRoHavGlruok1azc
bing.com
TXT
v=msv1 t=6097A7EA-53F7-4028-BA76-6869CB284C54
bing.com
TXT
v=spf1 include:spf.protection.outlook.com -all

DNS propagation check of 'bing.com'Port scan + probeing of 'bing.com'TLS/SSL certificate check of 'bing.com'

References

References added from public DNS servers in 69ms
bing-com.mail.protection.outlook.com
A
52.101.11.0
bing-com.mail.protection.outlook.com
A
52.101.40.26
bing-com.mail.protection.outlook.com
A
52.101.42.0
bing-com.mail.protection.outlook.com
A
52.101.8.49

Log

+000
  • Recursive lookup starting at the root servers
+000
  • Starting lookup
+000
  • Querying 'a.root-servers.net' for ANY-records on 'bing.com'.
+025
+025
  • We are asked to query 'l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net, b.gtld-servers.net, f.gtld-servers.net, k.gtld-servers.net, m.gtld-servers.net, i.gtld-servers.net, g.gtld-servers.net, a.gtld-servers.net, c.gtld-servers.net, e.gtld-servers.net' for further details
+025
  • Try 'i.gtld-servers.net'
+025
  • Querying 'i.gtld-servers.net' for ANY-records on 'bing.com'.
+034
+034
  • We are asked to query 'dns1.p09.nsone.net, dns2.p09.nsone.net, dns3.p09.nsone.net, dns4.p09.nsone.net, ns1-204.azure-dns.com, ns2-204.azure-dns.net, ns4-204.azure-dns.info, ns3-204.azure-dns.org' for further details
+034
  • Try 'dns2.p09.nsone.net'
+034
  • No IP of 'dns2.p09.nsone.net' availible - look it up using public resolvers
+041
  • IP 198.51.45.9 found - answer from resolver2.opendns.com in 6ms.
+041
  • Querying 'dns2.p09.nsone.net' for ANY-records on 'bing.com'.
+049
+049
  • WRNRFC 8482 response recieved - NotImplemented
    RFC 8482 has been implemeneted by several DNS-servers in order to minimize DNS responses. They will deny responing to ANY-lookups. The lookup has been modified in order to get a useable result.
+049
  • Querying 'dns2.p09.nsone.net' for A-records on 'bing.com'.
+056
+056
  • Lookup of secondary query types
+056
  • Querying 'dns2.p09.nsone.net' for AAAA-records on 'bing.com'.
+078
+078
  • Querying 'dns2.p09.nsone.net' for MX-records on 'bing.com'.
+099
+099
  • Querying 'dns2.p09.nsone.net' for TXT-records on 'bing.com'.
+112
+113
  • Lookup done - got 8 records from 'dns2.p09.nsone.net' in a total of 112ms.
+113
  • Adding references
+113
  • All references are looked up using public DNS resolvers like Google, Cloudflare and openDNS.
+180
  • Looking for records on reference 'bing-com.mail.protection.outlook.com'. Got answer of 4 records in 66ms from 'resolver1.opendns.com'.
+181
  • All done - a total of 8 records retrived in 181ms. Main response from 'dns2.p09.nsone.net'.