AboutUs hasn't finished checking this site yet — the live checks below are current; more details appear as we crawl it.
bing.net
Verifying against the live site and live WHOIS/DNS…
Common questions
Is bing.net legit or a scam?
bing.net was registered Sep 3, 1997 (29 years old), per public registration records. AboutUs doesn't label sites "legit" or "a scam": this page lists the dated registration, DNS, HTTPS, mail-authentication and safety checks we could verify, each with its source, so you can decide for yourself.
Who owns bing.net?
Nobody has completed AboutUs's owner verification for bing.net. That's true of most sites here — it isn't itself a warning sign.
When was bing.net registered?
bing.net's registration dates to Sep 3, 1997 (29 years old), per public registration records. MarkMonitor Inc. is the registrar on record today.
Make sure the site responds over HTTPS with a valid certificate.
AboutUs has not vetted this site. Everything below is what we could measure automatically. Anything you do on the site — paying, sharing personal details, downloading — is between you and the site, not AboutUs.
Current facts
Latest available measurements; dated entries retain their dates. These are measurements, not an endorsement of the site.
latest result
Domain registered Sep 3, 1997 — 29 years old.
latest result
Registrar on record: MarkMonitor Inc. — unchanged since AboutUs began tracking (Sep 21, 2026).
Authority 73/100— ahead of 73% of the August 2026 scored sampleSome caution flags
Why this authority score
73 is a percentile: higher than 73% of sites we score.
How it's calculated
Prominence (Tranco rank #2,191)+10
Verified continuity: 29.2 years (RDAP registration)+11
Security & email hygiene+1
Calibration adjustment (published map)+15
Model score: 37/99 — what these reason lines add up to.
Published Authority (percentile): 73/100 — this site's rank against the August 2026 scored sample. Public Authority is capped at 99.
Safety evidence
No unexpired threat-feed result; name-similarity check available (recorded less than a day ago); 3/3 transport and email checks available (oldest recorded less than a day ago). This is evidence coverage, not a probability that a website is safe.
Recorded HTTPS check did not confirm a valid connection
No MX and no DMARC (mild)
Site history
Dated record — historical facts always carry their date.
1997
Domain registered (Sep 3, 1997).
2007
First tracked by AboutUs (Sep 14, 2007); profile edited 3 times through 2014.
✓ domain continuity 29 years registered– no HTTPS response the site did not answer over HTTPS when checked Nov 1, 2026
Lifeline · bing.net over time
Checked in the last 30 daysOlder, dated recordFrom registration records
Registered 29 years ago · on AboutUs since 2007 · 2 registrar changes since Jun 11, 2007 · 2 registrant changes since 2007 · last checked Nov 1, 2026.
Registration
RegisteredSep 3, 1997bing.net was registered on Sep 3, 1997.Source: RDAP, fetched Oct 25, 2026
AboutUs record
AboutUs wiki pageAboutUs wiki pageSep 14, 2007 – Apr 19, 2014An AboutUs wiki page described bing.net from Sep 14, 2007 to Apr 19, 2014 (3 edits).Source: AboutUs wiki archive, 2006–2023Current AboutUs recordJul 18, 2026 – Nov 1, 2026 (latest)
Registrar
CORE-96Jun 11, 2007 – Aug 3, 2007Registrar CORE-96 in the WHOIS and RDAP records held for bing.net, from Jun 11, 2007 to Aug 3, 2007.Source: WHOIS / RDAP archive (who.is)Markmonitor.comMay 22, 2009 – Sep 27, 2013Registrar Markmonitor.com in the WHOIS and RDAP records held for bing.net, from May 22, 2009 to Sep 27, 2013.
Registrant
Registrant recordsJun 11, 2007 – Jun 16, 2026Registration records for bing.net are held from Jun 11, 2007 to Jun 16, 2026 (493 records). 2 changes of registrant name or organization are marked. Privacy-service and redaction changes, renames of the same organization and new contacts at it are not counted.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Zone file
No nameserver records held, May 2012 – Jun 2013Nameservers: tal.deJun 11, 2007 – Apr 6, 2009Registration records listed tal.de nameservers (pns.tal.de, sns.tal.de) for bing.net from Jun 11, 2007 to Apr 6, 2009.Source: From registration records (WHOIS / RDAP archive, who.is)
Certificate
Microsoft CorporationMicrosoft CorporationDec 23, 2025 – Nov 1, 2026Microsoft Corporation issued 196 certificates for bing.net from Dec 23, 2025, the latest valid until Apr 28, 2027.Source: Certificate Transparency logs (AboutUs's own certificate-log reader)
200020102020Jan ’26Oct ’26← last 12 months, drawn wider
Every dated fact on this lifeline (21)
Sep 3, 1997Registration: bing.net was registered on Sep 3, 1997.Source: RDAP, fetched Oct 25, 2026
Jun 11, 2007 – Aug 3, 2007Registrar: Registrar CORE-96 in the WHOIS and RDAP records held for bing.net, from Jun 11, 2007 to Aug 3, 2007.Source: WHOIS / RDAP archive (who.is)
Jun 11, 2007 – Jun 16, 2026Registrant: Registration records for bing.net are held from Jun 11, 2007 to Jun 16, 2026 (493 records). 2 changes of registrant name or organization are marked. Privacy-service and redaction changes, renames of the same organization and new contacts at it are not counted.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Jun 11, 2007 – Apr 6, 2009Zone file: Registration records listed tal.de nameservers (pns.tal.de, sns.tal.de) for bing.net from Jun 11, 2007 to Apr 6, 2009.Source: From registration records (WHOIS / RDAP archive, who.is)
Sep 14, 2007 – Apr 19, 2014AboutUs record: An AboutUs wiki page described bing.net from Sep 14, 2007 to Apr 19, 2014 (3 edits).Source: AboutUs wiki archive, 2006–2023
Apr 4, 2009Registrant: The registrant name or organization in the registration record changed; first recorded Apr 4, 2009. That can be a rename, a new contact or a sale; the record alone does not say which.
Authority and Safety last refreshed Nov 1, 2026.
Source: AboutUs checks
Source: WHOIS / RDAP archive (who.is)
MarkMonitor, Inc.MarkMonitor, Inc.Nov 21, 2013 – Sep 21, 2026 (latest)Registrar MarkMonitor, Inc. (IANA 292) in the registration data recorded, first on Nov 21, 2013 and most recently on Sep 21, 2026.Source: RDAP, fetched Oct 25, 2026
Registrant change
Apr 4, 2009
The registrant name or organization in the registration record changed; first recorded Apr 4, 2009. That can be a rename, a new contact or a sale; the record alone does not say which.
Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Registrant changeNov 21, 2013The registrant name or organization in the registration record changed; first recorded Nov 21, 2013. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
2 registrant changes, 2007–2026
Nameservers: msft.netApr 8, 2009 – May 1, 2012Registration records listed msft.net nameservers (ns1.msft.net, ns2.msft.net, ns3.msft.net…) for bing.net from Apr 8, 2009 to May 1, 2012.Source: From registration records (WHOIS / RDAP archive, who.is)
DNS moved to msft.netApr 8, 2009bing.net's nameservers moved from tal.de to msft.net between Apr 6, 2009 and Apr 8, 2009. Last seen at tal.de: Apr 6, 2009 (registration record). First seen at msft.net: Apr 8, 2009 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Nameservers: msedge.netJun 5, 2013 – Oct 17, 2013Registration records listed msedge.net nameservers (ns1.msedge.net) for bing.net from Jun 5, 2013 to Oct 17, 2013. Days a zone file covers are shown from the zone file instead.Source: From registration records (WHOIS / RDAP archive, who.is)
DNS moved to msedge.netJun 5, 2013bing.net's nameservers moved from msft.net to msedge.net at some point between May 1, 2012 and Jun 5, 2013. Last seen at msft.net: May 1, 2012 (registration record). First seen at msedge.net: Jun 5, 2013 (registration record). AboutUs holds no nameserver records for the 13 months in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Nameservers: msedge.netOct 18, 2013 – Apr 3, 2018msedge.net (ns1.msedge.net, ns2.msedge.net, ns3.msedge.net…) were the nameservers listed for bing.net at every ICANN zone-file snapshot AboutUs holds from Oct 18, 2013 to Apr 3, 2018 (snapshots exist for only part of 2013–2018).Source: ICANN zone-file snapshots, 2013–2018 (legacy archive)
Nameservers: msedge.netApr 4, 2018 – Jul 20, 2018Registration records listed msedge.net nameservers (ns1.msedge.net) for bing.net from Apr 4, 2018 to Jul 20, 2018. Days a zone file covers are shown from the zone file instead.Source: From registration records (WHOIS / RDAP archive, who.is)
Nameservers: Microsoft Azure DNSAug 20, 2018 – Jul 29, 2019Registration records listed Microsoft Azure DNS nameservers (ns1-204.azure-dns.com, ns2-204.azure-dns.net, ns3-204.azure-dns.org…) for bing.net from Aug 20, 2018 to Jul 29, 2019.Source: From registration records (WHOIS / RDAP archive, who.is)
DNS moved to Microsoft Azure DNSAug 20, 2018bing.net's nameservers moved from msedge.net to Microsoft Azure DNS between Jul 20, 2018 and Aug 20, 2018. Last seen at msedge.net: Jul 20, 2018 (registration record). First seen at Microsoft Azure DNS: Aug 20, 2018 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Nameservers: NS1Nameservers: NS1Aug 27, 2019 – Jun 16, 2026Registration records listed NS1 nameservers (dns1.p03.nsone.net, ns1-204.azure-dns.com, ns2-204.azure-dns.net…) for bing.net from Aug 27, 2019 to Jun 16, 2026.Source: From registration records (WHOIS / RDAP archive, who.is)
DNS moved to NS1Aug 27, 2019bing.net's nameservers moved from Microsoft Azure DNS to NS1 between Jul 29, 2019 and Aug 27, 2019. Last seen at Microsoft Azure DNS: Jul 29, 2019 (registration record). First seen at NS1: Aug 27, 2019 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Apr 8, 2009 – May 1, 2012Zone file: Registration records listed msft.net nameservers (ns1.msft.net, ns2.msft.net, ns3.msft.net…) for bing.net from Apr 8, 2009 to May 1, 2012.Source: From registration records (WHOIS / RDAP archive, who.is)
Apr 8, 2009Zone file: bing.net's nameservers moved from tal.de to msft.net between Apr 6, 2009 and Apr 8, 2009. Last seen at tal.de: Apr 6, 2009 (registration record). First seen at msft.net: Apr 8, 2009 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)
May 22, 2009 – Sep 27, 2013Registrar: Registrar Markmonitor.com in the WHOIS and RDAP records held for bing.net, from May 22, 2009 to Sep 27, 2013.Source: WHOIS / RDAP archive (who.is)
Jun 5, 2013 – Oct 17, 2013Zone file: Registration records listed msedge.net nameservers (ns1.msedge.net) for bing.net from Jun 5, 2013 to Oct 17, 2013. Days a zone file covers are shown from the zone file instead.Source: From registration records (WHOIS / RDAP archive, who.is)
Jun 5, 2013Zone file: bing.net's nameservers moved from msft.net to msedge.net at some point between May 1, 2012 and Jun 5, 2013. Last seen at msft.net: May 1, 2012 (registration record). First seen at msedge.net: Jun 5, 2013 (registration record). AboutUs holds no nameserver records for the 13 months in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Oct 18, 2013 – Apr 3, 2018Zone file: msedge.net (ns1.msedge.net, ns2.msedge.net, ns3.msedge.net…) were the nameservers listed for bing.net at every ICANN zone-file snapshot AboutUs holds from Oct 18, 2013 to Apr 3, 2018 (snapshots exist for only part of 2013–2018).Source: ICANN zone-file snapshots, 2013–2018 (legacy archive)
Nov 21, 2013 – Sep 21, 2026Registrar: Registrar MarkMonitor, Inc. (IANA 292) in the registration data recorded, first on Nov 21, 2013 and most recently on Sep 21, 2026.Source: RDAP, fetched Oct 25, 2026
Nov 21, 2013Registrant: The registrant name or organization in the registration record changed; first recorded Nov 21, 2013. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Apr 4, 2018 – Jul 20, 2018Zone file: Registration records listed msedge.net nameservers (ns1.msedge.net) for bing.net from Apr 4, 2018 to Jul 20, 2018. Days a zone file covers are shown from the zone file instead.Source: From registration records (WHOIS / RDAP archive, who.is)
Aug 20, 2018 – Jul 29, 2019Zone file: Registration records listed Microsoft Azure DNS nameservers (ns1-204.azure-dns.com, ns2-204.azure-dns.net, ns3-204.azure-dns.org…) for bing.net from Aug 20, 2018 to Jul 29, 2019.Source: From registration records (WHOIS / RDAP archive, who.is)
Aug 20, 2018Zone file: bing.net's nameservers moved from msedge.net to Microsoft Azure DNS between Jul 20, 2018 and Aug 20, 2018. Last seen at msedge.net: Jul 20, 2018 (registration record). First seen at Microsoft Azure DNS: Aug 20, 2018 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Aug 27, 2019 – Jun 16, 2026Zone file: Registration records listed NS1 nameservers (dns1.p03.nsone.net, ns1-204.azure-dns.com, ns2-204.azure-dns.net…) for bing.net from Aug 27, 2019 to Jun 16, 2026.Source: From registration records (WHOIS / RDAP archive, who.is)
Aug 27, 2019Zone file: bing.net's nameservers moved from Microsoft Azure DNS to NS1 between Jul 29, 2019 and Aug 27, 2019. Last seen at Microsoft Azure DNS: Jul 29, 2019 (registration record). First seen at NS1: Aug 27, 2019 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Dec 23, 2025 – Nov 1, 2026Certificate: Microsoft Corporation issued 196 certificates for bing.net from Dec 23, 2025, the latest valid until Apr 28, 2027.Source: Certificate Transparency logs (AboutUs's own certificate-log reader)
Jul 18, 2026 – Nov 1, 2026AboutUs record: Authority and Safety last refreshed Nov 1, 2026.Source: AboutUs checks