petalcode.dev - robtex.com
petalcode.dev
| DNSSEC | ⚠️ Not signed | ||||||
| A | 2600:1901:0:7b4e::🇺🇸 Google2600:1901::/32 | ||||||
| A | 34.36.75.103🇺🇸 Google34.32.0.0/11 | ||||||
| NS | ns73.domaincontrol.com ⭐ | ||||||
| A | 2603:5:21a4::2f🇺🇸 GODADDY-DNS2603:5:21a0::/44 | ||||||
| PTR | ns73.domaincontrol.com | ||||||
| A | 97.74.106.47🇺🇸 GODADDY-DNS97.74.106.0/23 | ||||||
| PTR | ns73.domaincontrol.com | ||||||
| NS | ns74.domaincontrol.com | ||||||
| A | 2603:5:22a4::2f🇺🇸 GODADDY-DNS2603:5:22a0::/44 | ||||||
| PTR | ns74.domaincontrol.com | ||||||
| A | 173.201.74.47🇺🇸 GODADDY-DNS173.201.74.0/23 | ||||||
| PTR | ns74.domaincontrol.com | ||||||
| SOA | ns73.domaincontrol.comdns@jomax.net 2026-10-16 #13 | ||||||
dev
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns-tld1.charlestonroadregistry.com ⭐ | ||||||
| NS | ns-tld2.charlestonroadregistry.com | ||||||
| NS | ns-tld3.charlestonroadregistry.com | ||||||
| NS | ns-tld4.charlestonroadregistry.com | ||||||
| NS | ns-tld5.charlestonroadregistry.com | ||||||
| SOA | ns-tld1.charlestonroadregistry.comcloud-dns-hostmaster@google.com serial=1 | ||||||
Same first word
Similar names
Previous names
Next names
DNS History
8 records (4 active, 4 former)
●NSns73.domaincontrol.com2026-09-04 → 2026-11-07 · 2 obs
● 2026-11-07 16:25:30
●NSns74.domaincontrol.com2026-09-04 → 2026-11-07 · 2 obs
● 2026-11-07 16:25:30
○A15.197.148.332026-09-04 → 2026-09-04 · 3 obs
○ 2026-10-08 17:45:06
○ 2026-11-07 16:25:30
○A2600:1901:0:4057::2026-10-08 → 2026-10-08 · 4 obs
● 2026-10-08 17:45:06
○ 2026-10-20 23:13:58
○ 2026-11-07 16:25:30
●A2600:1901:0:7b4e::2026-10-20 → 2026-11-07 · 3 obs
● 2026-10-20 23:13:58
● 2026-11-07 16:25:30
○A3.33.130.1902026-09-04 → 2026-09-04 · 3 obs
○ 2026-10-08 17:45:06
○ 2026-11-07 16:25:30
●A34.36.75.1032026-10-20 → 2026-11-07 · 3 obs
● 2026-10-20 23:13:58
● 2026-11-07 16:25:30
○A8.232.220.542026-10-08 → 2026-10-08 · 4 obs
● 2026-10-08 17:45:06
○ 2026-10-20 23:13:58
○ 2026-11-07 16:25:30
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| dev | ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com... | - |
| petalcode.dev | ns74.domaincontrol.com, ns73.domaincontrol.com | - |
✅ Authoritative Response
Server:173.201.74.47
NS records: ns74.domaincontrol.com, ns73.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for petalcode.dev (unsigned zone)
⏱️ Timing
Total: 1300ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 34.36.75.103 |
| AAAA | 1 | 2600:1901:0:7b4e:: |
| NS | 2 | ns73.domaincontrol.com, ns74.domaincontrol.com |
| SOA | 1 | ns73.domaincontrol.com dns.jomax.net |
Analysis
IP Addresses
petalcode.dev directs to two IP numbers, 34.36.75.103 and 2600:1901:0:7b4e::
Host names like petalco.de are further examples that share IP numbers with petalcode.dev.
Name Servers
Two name servers handle the delegation for petalcode.dev: ns73.domaincontrol.com and ns74.domaincontrol.com.
petalcode.dev uses the same name servers as several other domains — among them htd-london.com, blockchaindynasty.com, cape-graphics.com and two more.
ns73.domaincontrol.com and ns74.domaincontrol.com both carry two IP addresses. The A records for ns73.domaincontrol.com are 97.74.106.47 and 2603:5:21a4::2f; the A records for ns74.domaincontrol.com are 173.201.74.47 and 2603:5:22a4::2f.