dns.pizza
Domain Intelligence Report

microsoftconnect.com

Full ownership history report — $29 at AboutUsCompare
Gathering intelligence... (0/12)
DNS
WHOIS
Security
Email
DNSSEC
Threats
Deliverability
SSL/TLS
HTTP
Tech Stack
Subdomains
Archive
Safe
Checking…
no attacks or spoofing
Up
Checking…
reachable and responding
Right
Set up Page Watch
it is what it is
Ready
Checking…
you see what's coming
Outline
Gathering data — check results will appear here as they complete.
DNS Records
WHOIS
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/TLS
Security
Email Auth
DNSSEC
Tech Stack
HTTP / Headers
Threats
Zone census
Subdomains
Web Archive
Deliverability

IPv6

Not checked yet. aaaa.bot has no recent IPv6 result for microsoftconnect.com. Run the check on aaaa.bot →

See where it lives on the IPv4 map →

Lineage

Our records: May 30, 2010 → Nov 13, 2026

Oldest registry snapshot we hold: 2010 · 0 renewals on record · DNS at Amazon Route 53 · 4 nameserver changes seen. These dates are when our records begin, not when the domain was registered.

Registrar

  • 2 earlier
    • BigRock Solutions Ltd
      Jun – Sep 2016
    • GoDaddy.com, LLC
      Nov 2016 – Mar 2021
  • DropCatch.com 418 LLC
    Jun 2018 – Mar 2019
  • Chengdu west dimension digital technology Co., LTD
    Jan 2020
  • Realtime Register B.v.
    Jun – Sep 2022
  • NameSilo, LLClast seen Jun 2023
    Jun 2023

DNS provider

  • GoDaddy
    Oct 2013 – Apr 2016
  • justhost.com
    Jan – Mar 2015
  • bodis.com
    Apr 2018
  • Amazon Route 53NOW
    Seen from Nov 2026
What changed (latest 8 of 13)
  1. Missing from the zone file, then back between Apr 3, 2018 and Nov 13, 2026Listed on 2018-04-03, missing from the next held snapshot, listed again on 2026-11-13. A registry hold also removes a name, so this is not proof it was dropped.
  2. DNS moved to Amazon Route 53 between Apr 3, 2018 and Nov 13, 2026ns1.bodis.com, ns2.bodis.com → ns-1400.awsdns-47.org, ns-1818.awsdns-35.co.uk, ns-231.awsdns-28.com, ns-740.awsdns-28.net.
  3. Re-registered between Sep 23, 2022 and Jun 13, 2023The name lapsed and was registered again through NameSilo, LLC. Expiry moved from 2022-12-02 to 2024-03-07.
  4. Re-registered between Mar 29, 2021 and Jun 27, 2022The name lapsed and was registered again through REALTIME REGISTER B.V. Expiry moved from 2021-07-15 to 2022-12-02.
  5. Re-registered between Jan 13, 2020 and Sep 24, 2020The name lapsed and was registered again through GoDaddy.com, LLC. Expiry moved from 2020-04-11 to 2021-07-15.
  6. Re-registered between Mar 12, 2019 and Jan 13, 2020The name lapsed and was registered again through Chengdu west dimension digital technology Co., LTD. Expiry moved from 2019-01-23 to 2020-04-11.
  7. Re-registered between Oct 14, 2017 and Jun 18, 2018The name lapsed and was registered again through DropCatch.com 418 LLC. Expiry moved from 2017-11-05 to 2019-01-23.
  8. DNS moved to bodis.com between Apr 1, 2016 and Apr 3, 2018ns69.domaincontrol.com, ns70.domaincontrol.com → ns1.bodis.com, ns2.bodis.com.

Solid bar: the stretch we observed that name. Dot: a single sighting. Dotted line: no record between sightings of the same name. Nothing is drawn between different names.

Registrar and renewals: 81 WHOIS/RDAP snapshots, 2010-05-30 to 2024-01-28 (ledger built 2026-09-27). Every renewal

DNS provider, registry zone files: 118 .com zone-file snapshots held, 2013-10-18 to 2026-11-13.

Want to know when microsoftconnect.com changes?

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

Monitor microsoftconnect.com

Explore related

TLD.com domainsIPv6Does microsoftconnect.com have IPv6?