dns.pizza
Domain Intelligence Report

bing.net

Full ownership history report — $29 at AboutUsCompare

IPv6

Measured 2026-11-01 16:19 UTC · aaaa.bot
D

The website has no IPv6.

bing.net has no IPv6 address published.

  • ✗ bing.net: no IPv6 address
  • ✗ www.bing.net: no IPv6 address
  • ✗ Mail: 0 of 0 servers have IPv6
  • ✓ Nameservers: 8 of 8 have IPv6
Details: published addresses and what answered
bing.netPublishedno IPv6 address publishedAnswers when we connectnothing to test
www.bing.netPublishedno IPv6 address publishedAnswers when we connectnothing to test
MailPublishedNo MX records, so mail goes to the domain's own address (implicit MX). It has no AAAA record.Answers when we connectsee detail
NameserversPublishedns1-204.azure-dns.comns2-204.azure-dns.netns3-204.azure-dns.orgns4-204.azure-dns.infodns1.p08.nsone.netdns2.p08.nsone.netdns3.p08.nsone.netdns4.p08.nsone.netAnswers when we connect✓ has IPv6✓ has IPv6✓ has IPv6✓ has IPv6✓ has IPv6✓ has IPv6✓ has IPv6✓ has IPv6
First measured 2026-11-01: no IPv6 publishedIf this changes, the date will appear here.
Full check on aaaa.bot →Permanent receipt BMc_SdptUzJSON

Lineage

Our records: Jun 11, 2007 → Nov 1, 2026

Oldest registry snapshot we hold: 2007 · 18 renewals on record · DNS at Microsoft Azure DNS + NS1 · 4 nameserver changes seen. These dates are when our records begin, not when the domain was registered.

Registrar
489 snapshots
Markmonitor.comMarkMonitor, Inc.Renewed +1 yearbetween Jun 11, 2007 and Aug 3, 2007Expiry moved from 2006-09-02 to 2007-09-02, at CORE-96.Renewed +1 yearbetween Aug 3, 2007 and Nov 30, 2007Expiry moved from 2007-09-02 to 2008-09-02.Renewed +1 yearbetween Aug 8, 2008 and Sep 4, 2008Expiry moved from 2008-09-02 to 2009-09-02.Renewed +2 yearsbetween Apr 17, 2009 and May 22, 2009Expiry moved from 2009-09-02 to 2011-09-01, at Markmonitor.com.Renewed +1 yearbetween Jun 24, 2011 and Aug 18, 2011Expiry moved from 2011-09-01 to 2012-09-01, at Markmonitor.com.Renewed +1 yearbetween Jul 30, 2012 and Jan 7, 2013Expiry moved from 2012-09-01 to 2013-09-01, at Markmonitor.com.Renewed +1 yearbetween Jul 31, 2013 and Aug 16, 2013Expiry moved from 2013-09-01 to 2014-09-01, at Markmonitor.com.Renewed +2 yearsbetween Apr 17, 2014 and Jul 18, 2016Expiry moved from 2014-09-01 to 2016-09-01, at MarkMonitor, Inc.Renewed +1 yearbetween Jul 18, 2016 and Aug 1, 2016Expiry moved from 2016-09-01 to 2017-09-01, at MarkMonitor, Inc.Renewed +1 yearbetween Jul 30, 2017 and Aug 4, 2017Expiry moved from 2017-09-01 to 2018-09-01, at MarkMonitor, Inc.Renewed +1 yearbetween Jul 20, 2018 and Aug 20, 2018Expiry moved from 2018-09-01 to 2019-09-01, at MarkMonitor, Inc.Renewed +1 yearbetween Jul 29, 2019 and Aug 27, 2019Expiry moved from 2019-09-01 to 2020-09-01, at MarkMonitor, Inc.Renewed +1 yearbetween Jul 20, 2020 and Aug 7, 2020Expiry moved from 2020-09-01 to 2021-09-01, at MarkMonitor, Inc.Renewed +1 yearbetween Jul 6, 2021 and Aug 6, 2021Expiry moved from 2021-09-01 to 2022-09-01, at MarkMonitor, Inc.Renewed +1 yearbetween Jul 23, 2022 and Aug 9, 2022Expiry moved from 2022-09-01 to 2023-09-02, at MarkMonitor, Inc.Renewed +1 yearbetween Jul 11, 2023 and Aug 10, 2023Expiry moved from 2023-09-02 to 2024-09-02, at MarkMonitor, Inc.Renewed +1 yearbetween Jul 26, 2024 and Aug 12, 2024Expiry moved from 2024-09-02 to 2025-09-02, at MarkMonitor, Inc.Renewed +1 yearbetween Jul 21, 2025 and Aug 7, 2025Expiry moved from 2025-09-02 to 2026-09-02, at MarkMonitor, Inc.
Nameservers
registry zone files
DNS moved to msedge.netbetween Apr 17, 2009 and Oct 18, 2013ns1.msft.net, ns2.msft.net, ns3.msft.net, ns4.msft.net, ns5.msft.net → ns1.msedge.net, ns2.msedge.net, ns3.msedge.net, ns4.msedge.net. Old set last seen in WHOIS on 2009-04-17; new set first in the registry zone file on 2013-10-18.
seen in WHOIS
Microsoft Azure DNS + NS1DNS moved to msft.netbetween Apr 6, 2009 and Apr 8, 2009pns.tal.de, sns.tal.de → ns1.msft.net, ns2.msft.net, ns3.msft.net, ns4.msft.net, ns5.msft.net. Old set last seen in WHOIS on 2009-04-06; new set first seen in WHOIS on 2009-04-08.DNS moved to Microsoft Azure DNSbetween Jul 20, 2018 and Aug 20, 2018ns1.msedge.net, ns2.msedge.net, ns3.msedge.net, ns4.msedge.net → ns1-204.azure-dns.com, ns2-204.azure-dns.net, ns3-204.azure-dns.org, ns4-204.azure-dns.info. Old set last seen in WHOIS on 2018-07-20; new set first seen in WHOIS on 2018-08-20.DNS moved to Microsoft Azure DNS + NS1between Jul 29, 2019 and Aug 27, 2019ns1-204.azure-dns.com, ns2-204.azure-dns.net, ns3-204.azure-dns.org, ns4-204.azure-dns.info → dns1.p03.nsone.net, ns1-204.azure-dns.com, ns2-204.azure-dns.net, ns3-204.azure-dns.org, ns4-204.azure-dns.info. Old set last seen in WHOIS on 2019-07-29; new set first seen in WHOIS on 2019-08-27.
IPv6
aaaa.bot check
2011201520192026
What changed (latest 8 of 23)
  1. IPv6 first measured: no IPv6 published on Nov 1, 2026bing.net: no IPv6 published. Grade D. Measured by aaaa.bot, 2026-11-01 16:19 UTC. No earlier IPv6 record is held, so this is not a "gained" date.
  2. Renewed +1 year between Jul 21, 2025 and Aug 7, 2025Expiry moved from 2025-09-02 to 2026-09-02, at MarkMonitor, Inc.
  3. Renewed +1 year between Jul 26, 2024 and Aug 12, 2024Expiry moved from 2024-09-02 to 2025-09-02, at MarkMonitor, Inc.
  4. Renewed +1 year between Jul 11, 2023 and Aug 10, 2023Expiry moved from 2023-09-02 to 2024-09-02, at MarkMonitor, Inc.
  5. Renewed +1 year between Jul 23, 2022 and Aug 9, 2022Expiry moved from 2022-09-01 to 2023-09-02, at MarkMonitor, Inc.
  6. Renewed +1 year between Jul 6, 2021 and Aug 6, 2021Expiry moved from 2021-09-01 to 2022-09-01, at MarkMonitor, Inc.
  7. Renewed +1 year between Jul 20, 2020 and Aug 7, 2020Expiry moved from 2020-09-01 to 2021-09-01, at MarkMonitor, Inc.
  8. DNS moved to Microsoft Azure DNS + NS1 between Jul 29, 2019 and Aug 27, 2019ns1-204.azure-dns.com, ns2-204.azure-dns.net, ns3-204.azure-dns.org, ns4-204.azure-dns.info → dns1.p03.nsone.net, ns1-204.azure-dns.com, ns2-204.azure-dns.net, ns3-204.azure-dns.org, ns4-204.azure-dns.info. Old set last seen in WHOIS on 2019-07-29; new set first seen in WHOIS on 2019-08-27.

Registrar and renewals: 489 WHOIS/RDAP snapshots, 2007-06-11 to 2026-05-13 (ledger built 2026-09-27). Every renewal

Nameservers, registry zone files: 105 .net zone-file snapshots held, 2013-10-18 to 2026-11-01.

Nameservers, WHOIS snapshots: 343 WHOIS/RDAP snapshots that listed nameservers, 2007-06-11 to 2026-06-16 (who.is archive). A change is placed between the nearest observations on either side, from whichever source made them; where the two sources disagree, both are shown.

Hatched = the span we hold records for. A coloured bar runs only between observations that named the same registrar or operator; nothing is assumed in between.

Each mark sits at the first observation of the new state; its bracket runs back to the last observation of the old one.

Gathering intelligence... (12/12)
DNS
WHOIS
Security
Email
DNSSEC
Threats
Deliverability
SSL/TLS
HTTP
Tech Stack
Subdomains
Archive
Safe
DNSSEC unsigned
no attacks or spoofing
Up
HTTP 400
reachable and responding
Right
Set up Page Watch
it is what it is
Ready
140d ahead
you see what's coming
Outline
WHOIS
MarkMonitor Inc. · registered 29 years ago · expires Sep 2, 2027
DNS
1 A · 8 NS · 4 CAA · 1 PTR · 1 SOA · 1 TXT
SSL/TLS
invalid — Microsoft Corporation · TLSv1.3 · expires in 140d · 1 SANs
Email Auth
SPF ✗ · DKIM ✗ · DMARC ✗
DNSSEC
not signed
Tech Stack
Host: Microsoft Corporation · DNS: Azure DNS
HTTP
HTTP 400 · HSTS ✗ · CSP ✗ · X-Frame ✗ · Nosniff ✗
Security
C (135/215) · 3 critical · 1 high
Threats
risk: none
Deliverability
F (20/90) · 0 MX · 0 IPs · 4 issue(s)
Subdomains
wildcard DNS — every guessed name resolves
Web Archive
DNS Recordschecked 26.1d ago
Details
1 A · 8 NS · 4 CAA · 1 PTR · 1 SOA · 1 TXT
WHOISchecked 26.1d ago
Details
MarkMonitor Inc.
Registered 29 years ago
Expires Sep 2, 2027
Renewal history →
Then vs Nownew
No card for this name. We compare then and now for domains that are in the top million and had an AboutUs page. That says nothing about this domain’s age or safety.
Check what it is now →
SSL/TLSchecked 26.1d ago
Details
Invalid certificate
Issuer: Microsoft Corporation
Protocol: TLSv1.3
Expires in 140 days
1 SAN(s)
Securitychecked 26.1d ago
Details
C
135/215
3 critical1 high1 medium
Weakest: Record Security, Advanced Security
Email Authchecked 26.1d ago
Details
SPFDKIM?DMARC
DNSSECchecked 26.1d ago
Details
Not DNSSEC-signed
Tech Stackchecked 26.1d ago
Details
Microsoft CorporationDNS: Azure DNS
HTTP / Headerschecked 26.1d ago
Details
HSTSCSPX-FrameNosniff
Threatschecked 26.1d ago
Details
Risk: none · score 0
Zone census
Subdomainschecked 26.1d ago
Details
wildcard DNS — every name resolves, so a guessed-name inventory isn't meaningful
Click a subdomain for its full report
Web Archivechecked 26.1d ago
Details
First archived: unknown
Deliverabilitychecked 26.1d ago
Details
F
20/90 · 4 issue(s)
0 MX · 0 IP(s)
Top fix: No SPF record

Want to know when bing.net changes?

Monitor it free — 5 monitors, uptime checks every 5 minutes, email alerts when something breaks. No card required.

Monitor bing.net

Explore related

Registered in 1997 — the same year as google.com, facebook.com and mail.ru.

AgeDomains from 1997TLD.net domainsRegistrarMarkMonitor Inc.DNS providerazure-dns.com nameserversDNS providerazure-dns.net nameserversDNS providerazure-dns.org nameserversDNS providernsone.net nameserversIPv6Does bing.net have IPv6?