docs.parse.ly - dns.ninja
docs.parse.ly
| CNAME | wpvip.com | ||||||
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| A | 192.0.66.32🇺🇸 Automattic192.0.66.0/24 Route Object | ||||||
| NS | ns1.wordpress.com ⭐ | ||||||
| A | 2a04:fa87:ffff::c6b5:7409🇮🇪 Automattic2a04:fa87:ffff::/48 | ||||||
| PTR | ns1.wordpress.com | ||||||
| A | 198.181.116.9🇺🇸 Automattic198.181.116.0/24 Route Object | ||||||
| PTR | ns1.wordpress.com | ||||||
| NS | ns2.wordpress.com | ||||||
| A | 2a04:fa87:ffff::c6b5:7509🇮🇪 Automattic2a04:fa87:ffff::/48 | ||||||
| PTR | ns2.wordpress.com | ||||||
| A | 198.181.117.9🇺🇸 Automattic198.181.117.0/24 Route Object | ||||||
| PTR | ns2.wordpress.com | ||||||
| NS | ns3.wordpress.com | ||||||
| A | 2620:115:c00f::c000:4a09🇺🇸 Automattic2620:115:c00f::/48 Route6 Object | ||||||
| PTR | ns3.wordpress.com | ||||||
| A | 192.0.74.9🇺🇸 Automattic192.0.74.0/24 Route Object | ||||||
| PTR | ns3.wordpress.com | ||||||
| MX | mx1.dfw.automattic.com ⭐ | ||||||
| A | 192.0.84.151🇺🇸 Automattic192.0.84.0/24 Route Object | ||||||
| PTR | mx1.dfw.automattic.com | ||||||
| MX | mx2.ams.automattic.com ⭐ | ||||||
| A | 195.234.109.226🇳🇱 Automattic195.234.109.0/24 | ||||||
| PTR | mx2.ams.automattic.com | ||||||
| TXT | google-site-verification=87NLBQVtDhUNUkauU-DVwGTI0m2B1JodWgwn2SAyxbw | ||||||
| TXT | atlassian-domain-verification=HLvi8VknRfLwuOZ7TmiaKM8GgOgai45SxxeWZddVaOBMgWi... | ||||||
| TXT | ahrefs-site-verification_65c8058f68f935812e6a832c7dd303ae4cf11ffce55a4ff909e3... | ||||||
| TXT | google-site-verification=GcfqbF6RUtflCECrt9rrG7LCcvBao0GIme_Xv5m25xs | ||||||
| TXT | google-site-verification=J9DkGaUucwftRlIRqE9Q7Fhv_EsETFIIdN93Y8IPats | ||||||
| TXT | google-site-verification=rthC6ii3GP9m9DgpIA1uIm1FWjW9U7EtLa_bAzN0388 | ||||||
| TXT | adobe-idp-site-verification=a5492c56c4f6e7dfa7fa123d0036f0415402adfc279284334... | ||||||
| TXT | google-site-verification=Bv4fBOttOqRB9cqrFmLkd7k3xggNuhgwS6zccoi9CZI | ||||||
| TXT | v=spf1 include:_spf.automattic.com include:24337018.spf05.hubspotemail.net in... | ||||||
| SOA | ns1.wordpress.comhostmaster@wordpress.com 2005-07-18 #58 | ||||||
parse.ly
| DNSSEC | ⚠️ Not signed | ||||||
| A | 192.0.66.32🇺🇸 Automattic192.0.66.0/24 Route Object | ||||||
| NS | ns-1932.awsdns-49.co.uk ⭐ | ||||||
| NS | ns-1268.awsdns-30.org | ||||||
| NS | ns-270.awsdns-33.com | ||||||
| NS | ns-594.awsdns-10.net | ||||||
| MX | mx1.dfw.automattic.com ⭐ | ||||||
| MX | mx2.ams.automattic.com ⭐ | ||||||
| TXT | adobe-idp-site-verification=a5492c56c4f6e7dfa7fa123d0036f0415402adfc279284334... | ||||||
| TXT | google-site-verification=36S5smW4lixhZG7ZwdecXmrXamhX7BL3-hwDIu42eO8 | ||||||
| TXT | google-site-verification=KUmFi_sfjFoXK6VwXTVuiGm_47wT0mLSZ2JTKCus-Ck | ||||||
| TXT | v=spf1 include:_spf.automattic.com -all | ||||||
| SOA | ns-1932.awsdns-49.co.ukawsdns-hostmaster@amazon.com serial=1 | ||||||
WOT: SAFE (60/100)
rank #88099 globally
rank #41 in the tld
parse.ly
Parse.ly is a content analytics platform used by publishers and media companies to track audience engagement, traffic, and content performance. The domain also serves as a notable example of the.lyccTLD (Libya) being used as a wordplay domain hack for the English word "parsely"/"Parse.ly".
Key facts
- Owner / operator: Parse.ly, Inc. (acquired by Automattic in 2021)
- TLD:
.ly— Libya (ccTLD, popularly repurposed for domain hacks) - Primary purpose: content analytics and audience insights SaaS platform for digital publishers
- Status: active
History
| Year | Event |
|---|---|
| 2009 | Parse.ly founded |
| 2021 | Acquired by Automattic (parent company of WordPress.com) |
Related domains
automattic.com— parent companywordpress.com— sister property under Automattic
WOT: SAFE (61/100)
📈 Tranco rank: #192,825
Same first word
Similar names
DNS History
1 record (1 active, 0 former)
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| ly | pch.ltt.ly, ns-ly.afrinic.net, phloem.uoregon.edu, dns.lttnet.net... | 8 records |
| parse.ly | ns-594.awsdns-10.net, ns-1932.awsdns-49.co.uk, ns-270.awsdns-33.com, ns-1268.awsdns-30.org | - |
| parse.ly | ns-1268.awsdns-30.org, ns-1932.awsdns-49.co.uk, ns-270.awsdns-33.com, ns-594.awsdns-10.net | - |
| parse.ly | ns-1268.awsdns-30.org, ns-1932.awsdns-49.co.uk, ns-270.awsdns-33.com, ns-594.awsdns-10.net | - |
| parse.ly | ns-1268.awsdns-30.org, ns-1932.awsdns-49.co.uk, ns-270.awsdns-33.com, ns-594.awsdns-10.net | - |
| parse.ly | ns-1268.awsdns-30.org, ns-1932.awsdns-49.co.uk, ns-270.awsdns-33.com, ns-594.awsdns-10.net | - |
| parse.ly | ns-1268.awsdns-30.org, ns-1932.awsdns-49.co.uk, ns-270.awsdns-33.com, ns-594.awsdns-10.net | - |
| parse.ly | ns-1268.awsdns-30.org, ns-1932.awsdns-49.co.uk, ns-270.awsdns-33.com, ns-594.awsdns-10.net | - |
| parse.ly | ns-1268.awsdns-30.org, ns-1932.awsdns-49.co.uk, ns-270.awsdns-33.com, ns-594.awsdns-10.net | - |
| parse.ly | ns-1268.awsdns-30.org, ns-1932.awsdns-49.co.uk, ns-270.awsdns-33.com, ns-594.awsdns-10.net | - |
| parse.ly | ns-1268.awsdns-30.org, ns-1932.awsdns-49.co.uk, ns-270.awsdns-33.com, ns-594.awsdns-10.net | - |
| parse.ly | ns-1268.awsdns-30.org, ns-1932.awsdns-49.co.uk, ns-270.awsdns-33.com, ns-594.awsdns-10.net | - |
| parse.ly | ns-1268.awsdns-30.org, ns-1932.awsdns-49.co.uk, ns-270.awsdns-33.com, ns-594.awsdns-10.net | - |
| parse.ly | ns-1268.awsdns-30.org, ns-1932.awsdns-49.co.uk, ns-270.awsdns-33.com, ns-594.awsdns-10.net | - |
| parse.ly | ns-1268.awsdns-30.org, ns-1932.awsdns-49.co.uk, ns-270.awsdns-33.com, ns-594.awsdns-10.net | - |
| parse.ly | ns-1268.awsdns-30.org, ns-1932.awsdns-49.co.uk, ns-270.awsdns-33.com, ns-594.awsdns-10.net | - |
| parse.ly | ns-1268.awsdns-30.org, ns-1932.awsdns-49.co.uk, ns-270.awsdns-33.com, ns-594.awsdns-10.net | - |
| parse.ly | ns-1268.awsdns-30.org, ns-1932.awsdns-49.co.uk, ns-270.awsdns-33.com, ns-594.awsdns-10.net | - |
| parse.ly | ns-1268.awsdns-30.org, ns-1932.awsdns-49.co.uk, ns-270.awsdns-33.com, ns-594.awsdns-10.net | - |
| parse.ly | ns-1268.awsdns-30.org, ns-1932.awsdns-49.co.uk, ns-270.awsdns-33.com, ns-594.awsdns-10.net | - |
✅ Authoritative Response
Server:205.251.194.82
NS records: ns-1268.awsdns-30.org, ns-1932.awsdns-49.co.uk, ns-270.awsdns-33.com, ns-594.awsdns-10.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for parse.ly (unsigned zone)
⏱️ Timing
Total: 624ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| CNAME | 1 | wpvip.com |
📌 Glue Records Collected
Total: 8
In-bailiwick: 2 (pch.ltt.ly, pch.ltt.ly)
Out-of-bailiwick: 6 (ns-ly.afrinic.net, ns-ly.afrinic.net, phloem.uoregon.edu...)
Analysis
IP Addresses
docs.parse.ly has exactly one IP address — 192.0.66.32.
pagesix.com, www.go-vip.net, videojet.com.pl plus two other host names have IP numbers in common with docs.parse.ly.
Name Servers
DNS for docs.parse.ly is handled by three authoritative name servers: ns1.wordpress.com, ns2.wordpress.com and ns3.wordpress.com.
docs.parse.ly has at least partial name server overlap with other domains, such as anshulsushil.com, alphamale.com, annavanro.com and two others.
Three hostnames — ns1.wordpress.com, ns2.wordpress.com and ns3.wordpress.com — each have two IP addresses: ns1.wordpress.com has 198.181.116.9 and 2a04:fa87:ffff::c6b5:7409, ns2.wordpress.com has 198.181.117.9 and 2a04:fa87:ffff::c6b5:7509, and ns3.wordpress.com has 192.0.74.9 and 2620:115:c00f::c000:4a09.
Mail Servers
docs.parse.ly uses two mail servers, mx2.ams.automattic.com and mx1.dfw.automattic.com.
The mail server setup of docs.parse.ly matches that of other domains such as jetpackcrm.com, learnboost.com, polldaddy.net and two others.
docs.parse.ly has mail servers in common with other domains — for example blazepro.com, thepalmierireport.com and grupopresidente.com.mx.
mx2.ams.automattic.com directs to 195.234.109.226 and mx1.dfw.automattic.com directs to 192.0.84.151; each host name points to exactly one IP number.