Domain Intelligence Report
wpengine.com
IPv6
Measured 2026-11-01 05:13 UTC · aaaa.botD
The website has no IPv6.
wpengine.com has no IPv6 address published.
- ✗ wpengine.com: no IPv6 address
- ✗ www.wpengine.com: no IPv6 address
- ✓ Mail: 4 of 4 servers have IPv6
- ✓ Nameservers: 2 of 2 have IPv6
Details: published addresses and what answered
| Name | Published address (AAAA) | Answers when we connect |
|---|---|---|
| wpengine.com | Publishedno IPv6 address published | Answers when we connectnothing to test |
| www.wpengine.com | Publishedno IPv6 address published | Answers when we connectnothing to test |
Publishedaspmx.l.google.comaspmx2.googlemail.comaspmx3.googlemail.comalt2.aspmx.l.google.com | Answers when we connect✓ has IPv6✓ has IPv6✓ has IPv6✓ has IPv6 | |
| Nameservers | Publishedjim.ns.cloudflare.comkara.ns.cloudflare.com | Answers when we connect✓ has IPv6✓ has IPv6 |
First measured 2026-11-01: no IPv6 publishedIf this changes, the date will appear here.
Lineage
Our records: Mar 26, 2010 → Nov 1, 2026Oldest registry snapshot we hold: 2010 · 11 renewals on record · DNS at Cloudflare · 3 nameserver changes seen. These dates are when our records begin, not when the domain was registered.
Registrar
869 snapshots
NAMECHEAP INCMarkMonitor, Inc.Renewed +1 yearbetween Nov 30, 2010 and Apr 11, 2011Expiry moved from 2011-03-10 to 2012-03-10.Renewed +1 yearbetween Feb 8, 2012 and Feb 16, 2012Expiry moved from 2012-03-10 to 2013-03-10.Renewed +1 yearbetween Mar 11, 2013 and Mar 14, 2013Expiry moved from 2013-03-10 to 2014-03-10.Renewed +2 yearsbetween May 1, 2013 and May 15, 2013Expiry moved from 2014-03-10 to 2016-03-10.Moved to ENOM, INCbetween Sep 16, 2014 and Jun 29, 2016From REGISTER.COM, INC to ENOM, INC, with 1 year added. Expiry moved from 2016-03-10 to 2017-03-10.Renewed +1 yearbetween Feb 6, 2017 and Feb 10, 2017Expiry moved from 2017-03-10 to 2018-03-10, at ENOM, INC.Moved to NAMECHEAP INCbetween Dec 18, 2017 and Feb 11, 2018From ENOM, INC to NAMECHEAP INC, with 1 year added. Expiry moved from 2018-03-10 to 2019-03-10.Renewed +2 yearsbetween Jan 25, 2019 and Feb 19, 2019Expiry moved from 2019-03-10 to 2021-03-10, at NAMECHEAP INC.Moved to MarkMonitor, Incbetween Oct 28, 2019 and Nov 4, 2019From NAMECHEAP INC to MarkMonitor, Inc, with 2 years added. Expiry moved from 2021-03-10 to 2023-03-10.Renewed +2 yearsbetween Feb 7, 2023 and Feb 10, 2023Expiry moved from 2023-03-10 to 2025-03-10, at MarkMonitor, Inc.Renewed +2 yearsbetween Jan 10, 2025 and Feb 9, 2025Expiry moved from 2025-03-10 to 2027-03-10, at MarkMonitor, Inc.
Nameservers
registry zone files
DNS moved to Cloudflarebetween Sep 16, 2014 and Jan 24, 2015a.ns.zerigo.net, c.ns.zerigo.net, d.ns.zerigo.net, ns1.p14.dynect.net, ns3.p14.dynect.net → jim.ns.cloudflare.com, kara.ns.cloudflare.com. Old set last seen in WHOIS on 2014-09-16; new set first in the registry zone file on 2015-01-24.
seen in WHOIS
zerigo.netCloudflareDNS moved to zerigo.netbetween Mar 26, 2010 and Sep 8, 2010dns01.gpn.register.com, dns02.gpn.register.com, dns03.gpn.register.com, dns04.gpn.register.com, dns05.gpn.register.com → a.ns.zerigo.net, b.ns.zerigo.net, c.ns.zerigo.net, d.ns.zerigo.net, e.ns.zerigo.net. Old set last seen in WHOIS on 2010-03-26; new set first seen in WHOIS on 2010-09-08.DNS moved to Oracle Dyn + zerigo.netbetween Jun 27, 2013 and Jul 29, 2013a.ns.zerigo.net, b.ns.zerigo.net, c.ns.zerigo.net, d.ns.zerigo.net, e.ns.zerigo.net → a.ns.zerigo.net, c.ns.zerigo.net, d.ns.zerigo.net, ns1.p14.dynect.net, ns3.p14.dynect.net. Old set last seen in WHOIS on 2013-06-27; new set first seen in WHOIS on 2013-07-29.
IPv6
aaaa.bot check
2014201820222026
What changed (latest 8 of 15)
- IPv6 first measured: no IPv6 published on Nov 1, 2026wpengine.com: no IPv6 published. Grade D. Measured by aaaa.bot, 2026-11-01 05:13 UTC. No earlier IPv6 record is held, so this is not a "gained" date.
- Renewed +2 years between Jan 10, 2025 and Feb 9, 2025Expiry moved from 2025-03-10 to 2027-03-10, at MarkMonitor, Inc.
- Renewed +2 years between Feb 7, 2023 and Feb 10, 2023Expiry moved from 2023-03-10 to 2025-03-10, at MarkMonitor, Inc.
- Moved to MarkMonitor, Inc between Oct 28, 2019 and Nov 4, 2019From NAMECHEAP INC to MarkMonitor, Inc, with 2 years added. Expiry moved from 2021-03-10 to 2023-03-10.
- Renewed +2 years between Jan 25, 2019 and Feb 19, 2019Expiry moved from 2019-03-10 to 2021-03-10, at NAMECHEAP INC.
- Moved to NAMECHEAP INC between Dec 18, 2017 and Feb 11, 2018From ENOM, INC to NAMECHEAP INC, with 1 year added. Expiry moved from 2018-03-10 to 2019-03-10.
- Renewed +1 year between Feb 6, 2017 and Feb 10, 2017Expiry moved from 2017-03-10 to 2018-03-10, at ENOM, INC.
- Moved to ENOM, INC between Sep 16, 2014 and Jun 29, 2016From REGISTER.COM, INC to ENOM, INC, with 1 year added. Expiry moved from 2016-03-10 to 2017-03-10.
Registrar and renewals: 869 WHOIS/RDAP snapshots, 2010-03-26 to 2026-05-13 (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: 740 WHOIS/RDAP snapshots that listed nameservers, 2010-03-26 to 2026-06-14 (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
35d aheadyou see what's coming
Outline
WHOIS
MarkMonitor Inc. · registered 16 years ago · expires Mar 10, 2027
DNS
2 A · 4 MX · 2 NS · 1 SOA · 33 TXT
SSL/TLS
Google Trust Services · TLSv1.3 · expires in 35d · 2 SANs
Email Auth
SPF ✓ · DKIM ✓ · DMARC ✓ (p=reject)
DNSSEC
not signed
Tech Stack
CDN: Cloudflare · Email: Google Workspace · Cloudflare
HTTP
1 redirect → 200 · HSTS ✓ · CSP ✓ · X-Frame ✓ · Nosniff ✗
Security
B (165/215) · 2 high
Threats
risk: medium
Deliverability
A (94/100) · 4 MX · 8 IPs · 2 issue(s)
Subdomains
wildcard DNS — every guessed name resolves
Web Archive
DNS Recordschecked 2.1d ago
Details2 A · 4 MX · 2 NS · 1 SOA · 33 TXT
WHOISchecked 2.1d 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 2.1d ago
DetailsValid certificate
Issuer: Google Trust Services
Protocol: TLSv1.3
Expires in 35 days
2 SAN(s)
Securitychecked 2.1d ago
DetailsB
165/215
2 high
Weakest: Basic Security, Record Security
Email Authchecked 2.1d ago
DetailsSPFDKIMDMARC
Policy: reject
DNSSECchecked 2.1d ago
DetailsNot DNSSEC-signed
Tech Stackchecked 2.1d ago
DetailsCloudflareCloudflareEmail: Google WorkspaceGoogle Search ConsoleFacebook Domain VerificationApple BusinessDocuSignStripeHubSpot
HTTP / Headerschecked 2.1d ago
Details1 redirect(s) → 200
HSTSCSPX-FrameNosniff
Threatschecked 2.1d ago
DetailsRisk: medium · score 0.6999999999999998
Zone census
Subdomainschecked 2.1d ago
Detailswildcard DNS — every name resolves, so a guessed-name inventory isn't meaningful
Click a subdomain for its full report
Web Archivechecked 2.1d ago
DetailsFirst archived: unknown
Deliverabilitychecked 2.1d ago
DetailsA
94/100 · 2 issue(s)
4 MX · 8 IP(s)
Top fix: MX IP 2800:3f0:4003:c14::1a has no PTR (reverse DNS)
Want to know when wpengine.com changes?
Monitor it free — 50 monitors, uptime checks every 5 minutes, email alerts when something breaks. No card required.
Explore related
Registered in 2010 — the same year as t.me, dnsowl.com and cdn-apple.com.