I'm not trying to single out PagerDuty in being vulnerable. They run a particularly crucial service, and I'm sure they are doing everything they can to get out from under this.
That said, I still can't load www.pagerduty.com in a browser right now. :/
$ host -t NS pagerduty.com
pagerduty.com name server ns-219.awsdns-27.com.
pagerduty.com name server ns-739.awsdns-28.net.
pagerduty.com name server ns-1198.awsdns-21.org.
pagerduty.com name server ns-1569.awsdns-04.co.uk.
I think I'm satisfied.