piczly.com - robtex.com
piczly.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=1784400047 | ||||||
Same first word
piczly.com |
Similar names
DNS History
7 records (7 active, 0 former)
●NSdns1.registrar-servers.com2026-03-24 → 2026-07-18 · 2 obs
● 2026-07-18 18:51:50
●NSdns2.registrar-servers.com2026-03-24 → 2026-07-18 · 2 obs
● 2026-07-18 18:51:50
●MXeforward1.registrar-servers.com2026-03-24 → 2026-07-18 · 2 obs
● 2026-07-18 18:51:50
●MXeforward2.registrar-servers.com2026-03-24 → 2026-07-18 · 2 obs
● 2026-07-18 18:51:50
●MXeforward3.registrar-servers.com2026-03-24 → 2026-07-18 · 2 obs
● 2026-07-18 18:51:50
●MXeforward4.registrar-servers.com2026-03-24 → 2026-07-18 · 2 obs
● 2026-07-18 18:51:50
●MXeforward5.registrar-servers.com2026-03-24 → 2026-07-18 · 2 obs
● 2026-07-18 18:51:50
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | f.gtld-servers.net, g.gtld-servers.net, k.gtld-servers.net, m.gtld-servers.net... | - |
| piczly.com | dns1.registrar-servers.com, dns2.registrar-servers.com | 4 records |
✅ Authoritative Response
Server:156.154.132.200
NS records: dns1.registrar-servers.com, dns2.registrar-servers.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for piczly.com (unsigned zone)
⏱️ Timing
Total: 302ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | dns1.registrar-servers.com, dns2.registrar-servers.com |
| MX | 5 | eforward1.registrar-servers.com (pri: 10, eforward2.registrar-servers.com (pri: 10... |
| TXT | 1 | v=spf1 include:spf.efwd.registrar-server |
| SOA | 1 | dns1.registrar-servers.com hostmaster.re |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (dns1.registrar-servers.com, dns1.registrar-servers.com, dns2.registrar-servers.com...)
Analysis
Name Servers
piczly.com has two authoritative name servers — dns1.registrar-servers.com and dns2.registrar-servers.com.
piczly.com shares its NS records with other domains, for example davidsfork.org, moneyrain.com, 5854000.com and two others.
piczly.com shares at least some of its name servers with other domains, such as stamets.tv and moone.org.
Both dns1.registrar-servers.com and dns2.registrar-servers.com have two IP addresses each. dns1.registrar-servers.com resolves to 156.154.132.200 and 2610:a1:1024::200; dns2.registrar-servers.com resolves to 156.154.133.200 and 2610:a1:1025::200.
Mail Servers
piczly.com is handled by five mail servers: eforward1.registrar-servers.com, eforward2.registrar-servers.com, eforward3.registrar-servers.com and two others.
There is at least a partial MX overlap between piczly.com and other domains, including angryclover.com, telemato.com, fsestreamitk.today and two others.
eforward4.registrar-servers.com, eforward5.registrar-servers.com, eforward6.registrar-servers.com and eforward7.registrar-servers.com are mail servers that frequently appear together with these mail servers.
Host names that point to one IP address:
eforward1.registrar-servers.com resolves to 162.255.118.51.
eforward2.registrar-servers.com resolves to 162.255.118.52.
eforward3.registrar-servers.com resolves to 162.255.118.51.
eforward4.registrar-servers.com resolves to 162.255.118.52.
eforward5.registrar-servers.com resolves to 162.255.118.51.
Each of eforward1.registrar-servers.com, eforward3.registrar-servers.com and eforward5.registrar-servers.com resolves to 162.255.118.51.
The host names eforward2.registrar-servers.com and eforward4.registrar-servers.com both resolve to 162.255.118.52 IP addresses.