heroku.com
Lineage
Apr 24, 2009 → Oct 30, 2026Registry record since 2011 · 5 renewals on record · DNS at NS1 + herokudns.net · 6 nameserver changes seen.
What changed (latest 8 of 11)
- Renewed +2 years between May 1, 2025 and May 15, 2025Expiry moved from 2025-06-15 to 2027-06-15, at MarkMonitor, Inc.
- Renewed +2 years between May 4, 2023 and May 26, 2023Expiry moved from 2023-06-14 to 2025-06-15, at MarkMonitor, Inc.
- DNS moved to NS1 + herokudns.net between Feb 13, 2023 and Mar 5, 2023dns1.p04.nsone.net, dns2.p04.nsone.net, dns3.p04.nsone.net, dns4.p04.nsone.net → dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net, ns01.herokudns.net, ns02.herokudns.net, ns03.herokudns.net, ns04.herokudns.net. Old set last seen in WHOIS on 2023-02-13; new set first seen in WHOIS on 2023-03-05.
- DNS moved to NS1 between Feb 27, 2022 and Mar 3, 2022dns1.p04.nsone.net, dns2.p04.nsone.net, dns3.p04.nsone.net, dns4.p04.nsone.net, ns-1253.awsdns-28.org, ns-1538.awsdns-00.co.uk, ns-405.awsdns-50.com, ns-975.awsdns-57.net → dns1.p04.nsone.net, dns2.p04.nsone.net, dns3.p04.nsone.net, dns4.p04.nsone.net. Old set last seen in WHOIS on 2022-02-27; new set first seen in WHOIS on 2022-03-03.
- Renewed +2 years between Apr 15, 2021 and May 16, 2021Expiry moved from 2021-06-14 to 2023-06-14, at MarkMonitor, Inc.
- DNS moved to Amazon Route 53 + NS1 between Feb 11, 2020 and Feb 17, 2020dns1.p04.nsone.net, dns2.p04.nsone.net, dns3.p04.nsone.net, dns4.p04.nsone.net, ns-1253.awsdns-28.org, ns-1538.awsdns-00.co.uk, ns-405.awsdns-50.com, ns-975.awsdns-57.net, ns1.p19.dynect.net, ns2.p19.dynect.net, ns3.p19.dynect.net, ns4.p19.dynect.net → dns1.p04.nsone.net, dns2.p04.nsone.net, dns3.p04.nsone.net, dns4.p04.nsone.net, ns-1253.awsdns-28.org, ns-1538.awsdns-00.co.uk, ns-405.awsdns-50.com, ns-975.awsdns-57.net. Old set last seen in WHOIS on 2020-02-11; new set first seen in WHOIS on 2020-02-17.
- DNS moved to Amazon Route 53 + NS1 + Oracle Dyn between Jan 21, 2020 and Feb 11, 2020ns-1253.awsdns-28.org, ns-1538.awsdns-00.co.uk, ns-405.awsdns-50.com, ns-975.awsdns-57.net, ns1.p19.dynect.net, ns2.p19.dynect.net, ns3.p19.dynect.net, ns4.p19.dynect.net → dns1.p04.nsone.net, dns2.p04.nsone.net, dns3.p04.nsone.net, dns4.p04.nsone.net, ns-1253.awsdns-28.org, ns-1538.awsdns-00.co.uk, ns-405.awsdns-50.com, ns-975.awsdns-57.net, ns1.p19.dynect.net, ns2.p19.dynect.net, ns3.p19.dynect.net, ns4.p19.dynect.net. Old set last seen in WHOIS on 2020-01-21; new set first seen in WHOIS on 2020-02-11.
- Moved to MarkMonitor, Inc between Dec 15, 2016 and Dec 24, 2016From DYNAMIC NETWORK SERVICES, INC to MarkMonitor, Inc, with 2 years added. Expiry moved from 2019-06-15 to 2021-06-14.
Registrar and renewals: 413 WHOIS/RDAP snapshots, 2011-09-09 to 2026-05-16 (ledger built 2026-09-27). Every renewal
Nameservers, registry zone files: 103 .com zone-file snapshots held, 2013-10-18 to 2026-10-29.
Nameservers, WHOIS snapshots: 469 WHOIS/RDAP snapshots that listed nameservers, 2009-04-24 to 2026-06-30 (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.
Want to know when heroku.com changes?
Monitor it free — 50 monitors, uptime checks every 5 minutes, email alerts when something breaks. No card required.
Explore related
Registered in 2007 — the same year as fbcdn.net, github.com and youtu.be.