codebugged.com - dns.ninja
codebugged.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=1787420979 | ||||||
Same first word
codebugged.com |
Similar names
Previous names
Next names
DNS History
10 records (8 active, 2 former)
●NSns65.domaincontrol.com2019-12-17 → 2026-08-22 · 2 obs
● 2026-08-22 18:16:28
●NSns66.domaincontrol.com2019-12-17 → 2026-08-22 · 2 obs
● 2026-08-22 18:16:28
●MXalt1.aspmx.l.google.com2026-04-23 → 2026-08-22 · 2 obs
● 2026-08-22 18:16:28
●MXalt2.aspmx.l.google.com2026-04-23 → 2026-08-22 · 2 obs
● 2026-08-22 18:16:28
●MXalt3.aspmx.l.google.com2026-04-23 → 2026-08-22 · 2 obs
● 2026-08-22 18:16:28
●MXalt4.aspmx.l.google.com2026-04-23 → 2026-08-22 · 2 obs
● 2026-08-22 18:16:28
●MXaspmx.l.google.com2026-04-23 → 2026-08-22 · 2 obs
● 2026-08-22 18:16:28
○A13.233.117.1342019-12-17 → 2019-12-17 · 3 obs
○ 2026-04-23 18:00:06
○ 2026-08-22 18:16:28
○A139.59.91.372026-04-23 → 2026-04-23 · 4 obs
● 2026-04-23 18:00:06
○ 2026-08-19 17:44:30
○ 2026-08-22 18:16:28
●A143.110.248.1382026-08-19 → 2026-08-22 · 3 obs
● 2026-08-19 17:44:30
● 2026-08-22 18:16:28
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | f.gtld-servers.net, a.gtld-servers.net, i.gtld-servers.net, g.gtld-servers.net... | - |
| codebugged.com | ns66.domaincontrol.com, ns65.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:97.74.102.43
NS records: ns66.domaincontrol.com, ns65.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for codebugged.com (unsigned zone)
⏱️ Timing
Total: 316ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 143.110.248.138 |
| NS | 2 | ns65.domaincontrol.com, ns66.domaincontrol.com |
| MX | 5 | alt2.aspmx.l.google.com (pri: 5), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 6 | D7123518, google-site-verification=OVXGP0jggONGrqH... |
| SOA | 1 | ns65.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns66.domaincontrol.com, ns66.domaincontrol.com, ns65.domaincontrol.com...)
Analysis
IP Addresses
codebugged.com resolves to one IP address: 143.110.248.138.
Name Servers
codebugged.com has two authoritative name servers — ns65.domaincontrol.com and ns66.domaincontrol.com.
codebugged.com uses the same name servers as several other domains — among them hawaiiwednet.com, washingtonlawsuit.com, zewatchclub.com and two more.
Both ns65.domaincontrol.com and ns66.domaincontrol.com have two IP addresses each. ns65.domaincontrol.com resolves to 97.74.102.43 and 2603:5:2164::2b; ns66.domaincontrol.com resolves to 173.201.70.43 and 2603:5:2264::2b.
Mail Servers
codebugged.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
codebugged.com has at least partial mail server overlap with other domains such as 2cloud.com.au, steelgod.net, bnimmo.de and two more.
These mail servers commonly appear together with alt4.aspmx.l.google.com, alt3.aspmx.l.google.com, aspmx2.googlemail.com and two other mail servers.
Hostnames that resolve to two IP addresses:
aspmx.l.google.com resolves to 172.253.122.27 and 2607:f8b0:4004:c1b::1b.
alt1.aspmx.l.google.com resolves to 192.178.234.26 and 2800:3f0:4003:c14::1b.
alt2.aspmx.l.google.com resolves to 172.253.116.26 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com resolves to 192.178.223.27 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com resolves to 172.253.157.27 and 2a00:1450:400c:c23::1a.