pixieblush.com - dns.ninja
pixieblush.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 13.248.243.5🇺🇸 Amazon13.248.240.0/20 | ||||||
| PTR | a16e665f42988324c.awsglobalaccelerator.com | ||||||
| A | 76.223.105.230🇺🇸 Amazon76.223.96.0/20 | ||||||
| NS | ns75.domaincontrol.com ⭐ | ||||||
| A | 2603:5:21b4::30🇺🇸 GODADDY-DNS2603:5:21b0::/44 | ||||||
| PTR | ns75.domaincontrol.com | ||||||
| A | 97.74.107.48🇺🇸 GODADDY-DNS97.74.106.0/23 | ||||||
| PTR | ns75.domaincontrol.com | ||||||
| NS | ns76.domaincontrol.com | ||||||
| A | 2603:5:22b4::30🇺🇸 GODADDY-DNS2603:5:22b0::/44 | ||||||
| PTR | ns76.domaincontrol.com | ||||||
| A | 173.201.75.48🇺🇸 GODADDY-DNS173.201.74.0/23 | ||||||
| PTR | ns76.domaincontrol.com | ||||||
| SOA | ns75.domaincontrol.comdns@jomax.net 2026-02-01 #1 | ||||||
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1788739788 | ||||||
Same first word
pixieblush.co.uk |
pixieblush.com |
Similar names
Previous names
Next names
DNS History
12 records (4 active, 8 former)
○NSns-us.1and1-dns.com2015-08-02 → 2015-08-02 · 3 obs
○ 2015-11-28 03:11:10
○ 2026-09-07 00:21:56
○NSns-us.1and1-dns.de2015-08-02 → 2015-08-02 · 3 obs
○ 2015-11-28 03:11:10
○ 2026-09-07 00:21:56
○NSns-us.1and1-dns.org2015-08-02 → 2015-08-02 · 3 obs
○ 2015-11-28 03:11:10
○ 2026-09-07 00:21:56
○NSns-us.1and1-dns.us2015-08-02 → 2015-08-02 · 3 obs
○ 2015-11-28 03:11:10
○ 2026-09-07 00:21:56
●NSns75.domaincontrol.com2026-09-04 → 2026-09-07 · 3 obs
● 2026-09-04 02:51:08
● 2026-09-07 00:21:56
●NSns76.domaincontrol.com2026-09-04 → 2026-09-07 · 3 obs
● 2026-09-04 02:51:08
● 2026-09-07 00:21:56
○MXmx00.1and1.com2015-08-02 → 2015-08-02 · 3 obs
○ 2015-11-28 03:11:10
○ 2026-09-07 00:21:56
○MXmx01.1and1.com2015-08-02 → 2015-08-02 · 3 obs
○ 2015-11-28 03:11:10
○ 2026-09-07 00:21:56
●A13.248.243.52026-09-04 → 2026-09-07 · 3 obs
● 2026-09-04 02:51:08
● 2026-09-07 00:21:56
○A2607:f1c0:1000:1083:6ff9:f68f:8a54:58102015-08-02 → 2015-08-02 · 3 obs
○ 2015-11-28 03:11:10
○ 2026-09-07 00:21:56
○A74.208.57.752015-08-02 → 2015-08-02 · 3 obs
○ 2015-11-28 03:11:10
○ 2026-09-07 00:21:56
●A76.223.105.2302026-09-04 → 2026-09-07 · 3 obs
● 2026-09-04 02:51:08
● 2026-09-07 00:21:56
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| pixieblush.com | ns75.domaincontrol.com, ns76.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:97.74.107.48
NS records: ns75.domaincontrol.com, ns76.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for pixieblush.com (unsigned zone)
⏱️ Timing
Total: 199ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 76.223.105.230, 13.248.243.5 |
| NS | 2 | ns75.domaincontrol.com, ns76.domaincontrol.com |
| SOA | 1 | ns75.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns75.domaincontrol.com, ns75.domaincontrol.com, ns76.domaincontrol.com...)
Analysis
IP Addresses
pixieblush.com has two IP addresses: 13.248.243.5 and 76.223.105.230
Two other host names, along with snapshotsstudioevents.com, consciouscaresupport.com.au and rebeccalouise.co, also share IP numbers with pixieblush.com.
Name Servers
The NS records for pixieblush.com delegate to ns75.domaincontrol.com and ns76.domaincontrol.com.
pixieblush.com shares its NS records with other domains, for example comfortmedicaltransport.com, centerforbenefits.us, marisolroca.com and two others.
ns75.domaincontrol.com resolves to 97.74.107.48 and 2603:5:21b4::30. Likewise, ns76.domaincontrol.com resolves to 173.201.75.48 and 2603:5:22b4::30 — two IP addresses apiece.