bleedingpixel.com - robtex.com
bleedingpixel.com
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=1785451652 | ||||||
Same first word
bleedingpixel.com |
DNS History
10 records (9 active, 1 former)
●NSns17.domaincontrol.com2017-04-11 → 2026-07-30 · 2 obs
● 2026-07-30 22:49:32
●NSns18.domaincontrol.com2017-04-11 → 2026-07-30 · 2 obs
● 2026-07-30 22:49:32
●MXalt1.aspmx.l.google.com2017-04-11 → 2026-07-30 · 2 obs
● 2026-07-30 22:49:32
●MXalt2.aspmx.l.google.com2017-04-11 → 2026-07-30 · 2 obs
● 2026-07-30 22:49:32
●MXaspmx.l.google.com2017-04-11 → 2026-07-30 · 2 obs
● 2026-07-30 22:49:32
●MXaspmx2.googlemail.com2017-04-11 → 2026-07-30 · 2 obs
● 2026-07-30 22:49:32
●MXaspmx3.googlemail.com2017-04-11 → 2026-07-30 · 2 obs
● 2026-07-30 22:49:32
●A15.197.225.1282026-03-30 → 2026-07-30 · 3 obs
● 2026-03-30 05:20:12
● 2026-07-30 22:49:32
○A184.168.221.212017-04-11 → 2017-04-11 · 3 obs
○ 2026-03-30 05:20:12
○ 2026-07-30 22:49:32
●A3.33.251.1682026-03-30 → 2026-07-30 · 3 obs
● 2026-03-30 05:20:12
● 2026-07-30 22:49:32
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| bleedingpixel.com | ns17.domaincontrol.com, ns18.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.76.9
NS records: ns17.domaincontrol.com, ns18.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for bleedingpixel.com (unsigned zone)
⏱️ Timing
Total: 194ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 15.197.225.128, 3.33.251.168 |
| NS | 2 | ns17.domaincontrol.com, ns18.domaincontrol.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 2 | google-site-verification=A62V4zivciClrJN, v=spf1 include:_spf.google.com ~all |
| SOA | 1 | ns17.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns17.domaincontrol.com, ns17.domaincontrol.com, ns18.domaincontrol.com...)
Analysis
IP Addresses
bleedingpixel.com has two IP addresses: 3.33.251.168 and 15.197.225.128
Two other host names, along with ns211.ca, theleglamp.com and georgiaacuradealers.com, also share IP numbers with bleedingpixel.com.
Name Servers
bleedingpixel.com uses two name servers for its delegation: ns17.domaincontrol.com and ns18.domaincontrol.com.
bleedingpixel.com shares its NS records with other domains, for example sarahhinton.net, gojle.com, healingwithayahuasca.com and two others.
The two host names ns17.domaincontrol.com and ns18.domaincontrol.com each have a pair of IP addresses: ns17.domaincontrol.com has 97.74.108.9 and 2603:5:21c0::9, and ns18.domaincontrol.com has 173.201.76.9 and 2603:5:22c0::9.
Mail Servers
Five mail servers handle bleedingpixel.com: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
There is at least a partial MX overlap between bleedingpixel.com and other domains, including ns500731.ns500754.ns500671.ns500731.ns500742.ns500705.ns500688.ns500704.ns500649.ns500291.ns500142.lusty(0x736c7574)z.com, ourfuturecities.co, venygood.com and two others.
These mail servers tend to appear in combination with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.
Host names that have two IP addresses:
aspmx2.googlemail.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
aspmx3.googlemail.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com directs traffic to 142.251.163.27 and 2607:f8b0:4004:c1b::1a.
alt1.aspmx.l.google.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 2a00:1450:400b:c02::1a IP addresses each.