Domain Intelligence Report
waze.com
Lineage
Jun 7, 2007 → Oct 31, 2026Registry record since 2007 · 15 renewals on record · DNS at Google Domains · 6 nameserver changes seen.
Registrar
495 snapshots
MarkMonitor, Inc.Renewed +1 yearbetween Sep 30, 2007 and Jun 6, 2008Expiry moved from 2008-04-01 to 2009-04-01.Renewed +1 yearbetween Nov 28, 2008 and May 19, 2009Expiry moved from 2009-04-01 to 2010-04-01.Renewed +1 yearbetween Feb 22, 2010 and Mar 5, 2010Expiry moved from 2010-04-01 to 2011-04-01.Renewed +1 yearbetween Dec 21, 2010 and Mar 10, 2011Expiry moved from 2011-04-01 to 2012-04-01.Renewed +1 yearbetween Mar 1, 2012 and Mar 9, 2012Expiry moved from 2012-04-01 to 2013-04-01.Renewed +5 yearsbetween Mar 9, 2012 and Jun 19, 2016Expiry moved from 2013-04-01 to 2018-04-01, at MarkMonitor, Inc.Renewed +1 yearbetween Feb 21, 2018 and Mar 8, 2018Expiry moved from 2018-04-01 to 2019-04-01, at MarkMonitor, Inc.Renewed +1 yearbetween Feb 18, 2019 and Mar 6, 2019Expiry moved from 2019-04-01 to 2020-04-01, at MarkMonitor, Inc.Renewed +1 yearbetween Feb 24, 2020 and Mar 25, 2020Expiry moved from 2020-04-01 to 2021-04-01, at MarkMonitor, Inc.Renewed +1 yearbetween Jan 30, 2021 and Mar 4, 2021Expiry moved from 2021-04-01 to 2022-04-01, at MarkMonitor, Inc.Renewed +1 yearbetween Feb 14, 2022 and Mar 19, 2022Expiry moved from 2022-04-01 to 2023-04-01, at MarkMonitor, Inc.Renewed +1 yearbetween Feb 24, 2023 and Mar 1, 2023Expiry moved from 2023-04-01 to 2024-04-01, at MarkMonitor, Inc.Renewed +1 yearbetween Feb 13, 2024 and Mar 14, 2024Expiry moved from 2024-04-01 to 2025-04-01, at MarkMonitor, Inc.Renewed +1 yearbetween Feb 27, 2025 and Feb 28, 2025Expiry moved from 2025-04-01 to 2026-04-01, at MarkMonitor, Inc.Renewed +1 yearbetween Jan 21, 2026 and Mar 2, 2026Expiry moved from 2026-04-01 to 2027-04-01, at MarkMonitor, Inc.
Nameservers
registry zone files
DNS moved to Google Domainsbetween Mar 27, 2015 and Sep 23, 2015ns1.p25.dynect.net, ns2.p25.dynect.net, ns3.p25.dynect.net, ns4.p25.dynect.net → ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com.
seen in WHOIS
name-services.comGoogle DomainsDNS moved to hitfarm.combetween Jun 8, 2008 and Aug 7, 2008ns1.fastpark.net, ns2.fastpark.net → ns1.hitfarm.com, ns2.hitfarm.com. Old set last seen in WHOIS on 2008-06-08; new set first seen in WHOIS on 2008-08-07.DNS moved to fabulous.combetween Aug 7, 2008 and Sep 4, 2008ns1.hitfarm.com, ns2.hitfarm.com → ns1.fabulous.com, ns2.fabulous.com. Old set last seen in WHOIS on 2008-08-07; new set first seen in WHOIS on 2008-09-04.DNS moved to name-services.combetween Sep 4, 2008 and Oct 28, 2008ns1.fabulous.com, ns2.fabulous.com → dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com, dns5.name-services.com. Old set last seen in WHOIS on 2008-09-04; new set first seen in WHOIS on 2008-10-28.DNS moved to Oracle Dynbetween Dec 26, 2011 and Mar 1, 2012dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com, dns5.name-services.com → ns1.p25.dynect.net, ns2.p25.dynect.net, ns3.p25.dynect.net, ns4.p25.dynect.net. Old set last seen in WHOIS on 2011-12-26; new set first seen in WHOIS on 2012-03-01.New nameservers at Google Domainsbetween Aug 11, 2025 and Sep 13, 2025ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com → ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com. Old set last seen in WHOIS on 2025-08-11; new set first seen in WHOIS on 2025-09-13.
2011201520192026
What changed (latest 8 of 21)
- Renewed +1 year between Jan 21, 2026 and Mar 2, 2026Expiry moved from 2026-04-01 to 2027-04-01, at MarkMonitor, Inc.
- New nameservers at Google Domains between Aug 11, 2025 and Sep 13, 2025ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com → ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com. Old set last seen in WHOIS on 2025-08-11; new set first seen in WHOIS on 2025-09-13.
- Renewed +1 year between Feb 27, 2025 and Feb 28, 2025Expiry moved from 2025-04-01 to 2026-04-01, at MarkMonitor, Inc.
- Renewed +1 year between Feb 13, 2024 and Mar 14, 2024Expiry moved from 2024-04-01 to 2025-04-01, at MarkMonitor, Inc.
- Renewed +1 year between Feb 24, 2023 and Mar 1, 2023Expiry moved from 2023-04-01 to 2024-04-01, at MarkMonitor, Inc.
- Renewed +1 year between Feb 14, 2022 and Mar 19, 2022Expiry moved from 2022-04-01 to 2023-04-01, at MarkMonitor, Inc.
- Renewed +1 year between Jan 30, 2021 and Mar 4, 2021Expiry moved from 2021-04-01 to 2022-04-01, at MarkMonitor, Inc.
- Renewed +1 year between Feb 24, 2020 and Mar 25, 2020Expiry moved from 2020-04-01 to 2021-04-01, at MarkMonitor, Inc.
Registrar and renewals: 495 WHOIS/RDAP snapshots, 2007-06-07 to 2026-05-18 (ledger built 2026-09-27). Every renewal
Nameservers, registry zone files: 105 .com zone-file snapshots held, 2013-10-18 to 2026-10-31.
Nameservers, WHOIS snapshots: 435 WHOIS/RDAP snapshots that listed nameservers, 2007-06-07 to 2026-06-28 (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.
Gathering intelligence... (12/12)
DNS
WHOIS
Security
Email
DNSSEC
Threats
Deliverability
SSL/TLS
HTTP
Tech Stack
Subdomains
Archive
Safe
2 concernsno attacks or spoofing
Up
HTTP 200reachable and responding
Right
Set up Page Watchit is what it is
Ready
84d aheadyou see what's coming
Outline
WHOIS
MarkMonitor Inc. · registered 26 years ago · expires Apr 1, 2027
DNS
1 A · 5 MX · 4 NS · 2 CAA · 1 PTR · 1 SOA · 9 TXT · 1 AAAA
SSL/TLS
Google Trust Services · TLSv1.3 · expires in 84d · 6 SANs
Email Auth
SPF ✓ · DKIM ✓ · DMARC ✓ (p=reject)
DNSSEC
not signed
Tech Stack
Host: Google LLC · Email: Google Workspace · DNS: Google Cloud DNS
HTTP
2 redirect → 200 · HSTS ✓ · CSP ✓ · X-Frame ✓ · Nosniff ✓
Security
A (195/225) · 1 high
Threats
risk: medium
Deliverability
A (90/100) · 5 MX · 10 IPs · 3 issue(s)
Subdomains
wildcard DNS — every guessed name resolves
Web Archive
first snapshot 1999-10-12 · 27y archived
DNS Recordschecked 1.8d ago
Details1 A · 5 MX · 4 NS · 2 CAA · 1 PTR · 1 SOA · 9 TXT · 1 AAAA
WHOISchecked 1.8d ago
DetailsThen 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/TLSchecked 1.8d ago
DetailsValid certificate
Issuer: Google Trust Services
Protocol: TLSv1.3
Expires in 84 days
6 SAN(s)
Securitychecked 1.8d ago
DetailsA
195/225
1 high
Weakest: Basic Security, Record Security
Email Authchecked 1.8d ago
DetailsSPFDKIMDMARC
Policy: reject
DNSSECchecked 1.8d ago
DetailsNot DNSSEC-signed
Tech Stackchecked 1.8d ago
DetailsGoogle LLCEmail: Google WorkspaceDNS: Google Cloud DNSGoogle Search Console
HTTP / Headerschecked 1.8d ago
Details2 redirect(s) → 200
HSTSCSPX-FrameNosniff
Threatschecked 1.8d ago
DetailsRisk: medium · score 0.6999999999999998
Zone census
Subdomainschecked 1.8d ago
Detailswildcard DNS — every name resolves, so a guessed-name inventory isn't meaningful
Click a subdomain for its full report
Web Archivechecked 1.8d ago
DetailsFirst archived: 1999-10-12
~27 years of history
Deliverabilitychecked 1.8d ago
DetailsA
90/100 · 3 issue(s)
5 MX · 10 IP(s)
Top fix: MX IP 2800:3f0:4003:c14::1b has no PTR (reverse DNS)
Want to know when waze.com changes?
Monitor it free — 50 monitors, uptime checks every 5 minutes, email alerts when something breaks. No card required.
Explore related
Registered in 2000 — the same year as twitter.com, yandex.net and wordpress.com.