IPv6
Not checked yet. aaaa.bot has no recent IPv6 result for com.be. Run the check on aaaa.bot →
Lineage
Our records: Jan 17, 2009 → Jun 5, 2026These dates are when our records begin, not when the domain was registered.
DNS provider
10 earlier
- websitewelcome.comJan – Apr 2009
- jnprk.comMay – Jun 2009
- dwhltd.comJul 2009 – Aug 2011
- affsrvr.comNov 2011 – Jul 2013
- BluehostSep 2013 – Jan 2016
- paltrics.comAug – Dec 2015
- sedoparking.comDec 2015
- siteland.beMar 2016 – Dec 2019
- GoDaddyOct 2016
- websiteland.beNov 2016
- com.beApr 2017 – Mar 2020
- comlaude.ch + comlaude.co.uk + comlaude.netJun 2020 – Sep 2021
- Oracle Dyn + UltraDNS (Neustar/Vercara) + ultradns.co.ukOct 2021 – May 2023
- amzndns.co.uk + amzndns.com + amzndns.net + amzndns.orgMay 2023 – Jun 2026
What changed (latest 8 of 14)
- DNS moved to amzndns.co.uk + amzndns.com + amzndns.net + amzndns.org between May 18, 2023 and May 31, 2023ns1.p31.dynect.net, ns2.p31.dynect.net, ns3.p31.dynect.net, ns4.p31.dynect.net, pdns1.ultradns.net, pdns2.ultradns.net, pdns3.ultradns.org, pdns5.ultradns.info, pdns6.ultradns.co.uk → ns1.amzndns.co.uk, ns1.amzndns.com, ns1.amzndns.net, ns1.amzndns.org, ns2.amzndns.co.uk, ns2.amzndns.com, ns2.amzndns.net, ns2.amzndns.org. Old set last seen in WHOIS on 2023-05-18; new set first seen in WHOIS on 2023-05-31.
- DNS moved to Oracle Dyn + UltraDNS (Neustar/Vercara) + ultradns.co.uk between Sep 16, 2021 and Oct 31, 2021nsgbr.comlaude.co.uk, nssui.comlaude.ch, nsusa.comlaude.net → ns1.p31.dynect.net, ns2.p31.dynect.net, ns3.p31.dynect.net, ns4.p31.dynect.net, pdns1.ultradns.net, pdns2.ultradns.net, pdns3.ultradns.org, pdns5.ultradns.info, pdns6.ultradns.co.uk. Old set last seen in WHOIS on 2021-09-16; new set first seen in WHOIS on 2021-10-31.
- DNS moved to comlaude.ch + comlaude.co.uk + comlaude.net between Mar 27, 2020 and Jun 9, 2020a.ns.dns.com.be, b.ns.dns.com.be, c.ns.dns.com.be → nsgbr.comlaude.co.uk, nssui.comlaude.ch, nsusa.comlaude.net. Old set last seen in WHOIS on 2020-03-27; new set first seen in WHOIS on 2020-06-09.
- DNS moved to com.be between Dec 9, 2019 and Jan 27, 2020ns1.siteland.be, ns2.siteland.be → a.ns.dns.com.be, b.ns.dns.com.be, c.ns.dns.com.be. Old set last seen in WHOIS on 2019-12-09; new set first seen in WHOIS on 2020-01-27.
- DNS moved to siteland.be between Sep 22, 2018 and Oct 31, 2018ns1.com.be, ns2.com.be → ns1.siteland.be, ns2.siteland.be. Old set last seen in WHOIS on 2018-09-22; new set first seen in WHOIS on 2018-10-31.
- DNS moved to com.be between Nov 2, 2016 and Apr 10, 2017ns1.websiteland.be, ns2.websiteland.be → ns1.com.be, ns2.com.be. Old set last seen in WHOIS on 2016-11-02; new set first seen in WHOIS on 2017-04-10.
- DNS moved to websiteland.be between Sep 8, 2016 and Nov 2, 2016ns1.siteland.be, ns2.siteland.be → ns1.websiteland.be, ns2.websiteland.be. Old set last seen in WHOIS on 2016-09-08; new set first seen in WHOIS on 2016-11-02.
- DNS moved to siteland.be between Jan 24, 2016 and Mar 1, 2016ns1.bluehost.com, ns2.bluehost.com → ns1.siteland.be, ns2.siteland.be. Old set last seen in WHOIS on 2016-01-24; new set first seen in WHOIS on 2016-03-01.
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.
DNS provider, WHOIS snapshots: 500 WHOIS/RDAP snapshots that listed nameservers, 2009-01-17 to 2026-06-05 (who.is archive). Both sources feed one row per provider (hover a bar to see which); a change is placed between the nearest observations on either side, and where the two sources disagree, both are listed under What changed.
Want to know when com.be changes?
Monitor it free — 5 monitors, uptime checks every 5 minutes, email alerts when something breaks. No card required.