blog.parseground.com - dns.ninja
blog.parseground.com
parseground.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 144.217.225.221🇨🇦 OVH144.217.0.0/16 Hosting route | ||||||
| NS | ns-4.awsdns-00.com ⭐ | ||||||
| NS | ns-1236.awsdns-26.org | ||||||
| NS | ns-1800.awsdns-33.co.uk | ||||||
| NS | ns-637.awsdns-15.net | ||||||
| MX | mx.parseground.com.cust.a.hostedemail.com ⭐ | ||||||
| TXT | v=spf1 include:spf.mandrillapp.com ?all | ||||||
| SOA | ns-4.awsdns-00.comawsdns-hostmaster@amazon.com serial=1 | ||||||
Same first word
Similar names
DNS History
1 record (1 active, 0 former)
●CNAMEd10mz1ppdfvt7o.cloudfront.net2026-03-19 → 2026-08-06 · 2 obs
● 2026-08-06 04:47:42
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | e.gtld-servers.net, i.gtld-servers.net, g.gtld-servers.net, a.gtld-servers.net... | - |
| parseground.com | ns-4.awsdns-00.com, ns-637.awsdns-15.net, ns-1800.awsdns-33.co.uk, ns-1236.awsdns-26.org | 2 records |
| parseground.com | ns-1236.awsdns-26.org, ns-1800.awsdns-33.co.uk, ns-4.awsdns-00.com, ns-637.awsdns-15.net | - |
| parseground.com | ns-1236.awsdns-26.org, ns-1800.awsdns-33.co.uk, ns-4.awsdns-00.com, ns-637.awsdns-15.net | - |
| parseground.com | ns-1236.awsdns-26.org, ns-1800.awsdns-33.co.uk, ns-4.awsdns-00.com, ns-637.awsdns-15.net | - |
| parseground.com | ns-1236.awsdns-26.org, ns-1800.awsdns-33.co.uk, ns-4.awsdns-00.com, ns-637.awsdns-15.net | - |
| parseground.com | ns-1236.awsdns-26.org, ns-1800.awsdns-33.co.uk, ns-4.awsdns-00.com, ns-637.awsdns-15.net | - |
| parseground.com | ns-1236.awsdns-26.org, ns-1800.awsdns-33.co.uk, ns-4.awsdns-00.com, ns-637.awsdns-15.net | - |
| parseground.com | ns-1236.awsdns-26.org, ns-1800.awsdns-33.co.uk, ns-4.awsdns-00.com, ns-637.awsdns-15.net | - |
| parseground.com | ns-1236.awsdns-26.org, ns-1800.awsdns-33.co.uk, ns-4.awsdns-00.com, ns-637.awsdns-15.net | - |
| parseground.com | ns-1236.awsdns-26.org, ns-1800.awsdns-33.co.uk, ns-4.awsdns-00.com, ns-637.awsdns-15.net | - |
| parseground.com | ns-1236.awsdns-26.org, ns-1800.awsdns-33.co.uk, ns-4.awsdns-00.com, ns-637.awsdns-15.net | - |
| parseground.com | ns-1236.awsdns-26.org, ns-1800.awsdns-33.co.uk, ns-4.awsdns-00.com, ns-637.awsdns-15.net | - |
| parseground.com | ns-1236.awsdns-26.org, ns-1800.awsdns-33.co.uk, ns-4.awsdns-00.com, ns-637.awsdns-15.net | - |
| parseground.com | ns-1236.awsdns-26.org, ns-1800.awsdns-33.co.uk, ns-4.awsdns-00.com, ns-637.awsdns-15.net | - |
| parseground.com | ns-1236.awsdns-26.org, ns-1800.awsdns-33.co.uk, ns-4.awsdns-00.com, ns-637.awsdns-15.net | - |
| parseground.com | ns-1236.awsdns-26.org, ns-1800.awsdns-33.co.uk, ns-4.awsdns-00.com, ns-637.awsdns-15.net | - |
| parseground.com | ns-1236.awsdns-26.org, ns-1800.awsdns-33.co.uk, ns-4.awsdns-00.com, ns-637.awsdns-15.net | - |
| parseground.com | ns-1236.awsdns-26.org, ns-1800.awsdns-33.co.uk, ns-4.awsdns-00.com, ns-637.awsdns-15.net | - |
| parseground.com | ns-1236.awsdns-26.org, ns-1800.awsdns-33.co.uk, ns-4.awsdns-00.com, ns-637.awsdns-15.net | - |
| parseground.com | ns-1236.awsdns-26.org, ns-1800.awsdns-33.co.uk, ns-4.awsdns-00.com, ns-637.awsdns-15.net | - |
✅ Authoritative Response
Server:205.251.194.125
NS records: ns-1236.awsdns-26.org, ns-1800.awsdns-33.co.uk, ns-4.awsdns-00.com, ns-637.awsdns-15.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for parseground.com (unsigned zone)
⏱️ Timing
Total: 923ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| CNAME | 1 | d10mz1ppdfvt7o.cloudfront.net |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns-4.awsdns-00.com, ns-4.awsdns-00.com)
Analysis
IP Addresses
blog.parseground.com resolves to four IP addresses: 3.170.19.29, 3.170.19.38, 3.170.19.71 and 3.170.19.112.
Additional host names — www.bnchdev.org, auth.rocko.securityplatform.io, d3pcmnde77gg8b.cloudfront.net and two others — share IP numbers with blog.parseground.com.
Name Servers
blog.parseground.com has four authoritative name servers: ns-212.awsdns-26.com, ns-731.awsdns-27.net, ns-1412.awsdns-48.org and ns-1768.awsdns-29.co.uk.
blog.parseground.com has at least partial name server overlap with other domains, such as d2m329yquaos68.cloudfront.net, d2qn6k0n44oj9z.cloudfront.net, iyuigjo.com and two others.
ns-212.awsdns-26.com, ns-731.awsdns-27.net, ns-1412.awsdns-48.org and ns-1768.awsdns-29.co.uk all point to exactly two IP numbers each: ns-212.awsdns-26.com → 205.251.192.212 and 2600:9000:5300:d400::1; ns-731.awsdns-27.net → 205.251.194.219 and 2600:9000:5302:db00::1; ns-1412.awsdns-48.org → 205.251.197.132 and 2600:9000:5305:8400::1; ns-1768.awsdns-29.co.uk → 205.251.198.232 and 2600:9000:5306:e800::1.