nytimes.com is up, secure, and pointing to the right place. But this is just a snapshot — things break at 3am too.
Last checked just now from Dublin
We loaded nytimes.com once from Dublin. Here's where the 10 milliseconds went.
The padlock’s there. Visitors see a green padlock and browsers trust the certificate.
Most sites auto-renew these. We'll shout if yours forgets.
Visitors, bots, and email all end up in the right place. Nothing misconfigured.
This is how the internet finds nytimes.com. All looks normal.
Registered with MarkMonitor Inc.. Plenty of time before renewal.
nytimes.com resolves to 151.101.1.164. We checked from Dublin.
Uptime %, response times, SSL renewals, any incidents — all tracked over time so you can spot trends before they become problems.
DomainDash watches nytimes.com around the clock, from 8 regions around the world. If anything looks off — slow, broken, expiring — we tell you. That's the whole product.
We send you an alert straight away — by email on every plan, plus Slack and SMS on higher tiers. The alert includes which site, what went wrong, and when we first noticed. When your site comes back up, we let you know that too.
Yes — if you manage client sites, you can check them. You just need the domain name. No code changes or access to the server required.
One domain counts as one site. So acmecorp.com is one site. If you also check staging.acmecorp.com, that’s a second site.
Yes. No contracts, no cancellation fees. If you cancel a paid plan, you keep access until the end of your billing period, then your account reverts to the free tier.
DomainDash is built for freelancers and small teams, not DevOps engineers. We check uptime, SSL, DNS, and response speed in one place, with alerts in plain English — not technical jargon. And we’re priced so you don’t have to think twice about checking all your sites.
No. You just enter your domain name and we start checking it. No code snippets, no server access, no DNS changes.