codebell.com - robtex.com
codebell.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=1781290713 | ||||||
Subdomains
mail.codebell.com |
Same first word
Similar names
DNS History
12 records (10 active, 2 former)
●NSns-1455.awsdns-53.org2015-06-05 → 2026-06-12 · 2 obs
● 2026-06-12 19:03:26
●NSns-1614.awsdns-09.co.uk2015-06-05 → 2026-06-12 · 2 obs
● 2026-06-12 19:03:26
●NSns-194.awsdns-24.com2015-06-05 → 2026-06-12 · 2 obs
● 2026-06-12 19:03:26
●NSns-883.awsdns-46.net2015-06-05 → 2026-06-12 · 2 obs
● 2026-06-12 19:03:26
●MXalt1.aspmx.l.google.com2015-06-05 → 2026-06-12 · 2 obs
● 2026-06-12 19:03:26
●MXalt2.aspmx.l.google.com2015-06-05 → 2026-06-12 · 2 obs
● 2026-06-12 19:03:26
●MXalt3.aspmx.l.google.com2015-06-05 → 2026-06-12 · 2 obs
● 2026-06-12 19:03:26
●MXalt4.aspmx.l.google.com2015-06-05 → 2026-06-12 · 2 obs
● 2026-06-12 19:03:26
●MXaspmx.l.google.com2015-06-05 → 2026-06-12 · 2 obs
● 2026-06-12 19:03:26
●A23.236.62.1472015-12-30 → 2026-06-12 · 3 obs
● 2015-12-30 20:38:36
● 2026-06-12 19:03:26
○A54.234.69.2372015-10-25 → 2015-10-25 · 4 obs
● 2015-10-25 23:05:32
○ 2015-12-30 20:38:36
○ 2026-06-12 19:03:26
○A54.89.199.1982015-06-05 → 2015-06-05 · 3 obs
○ 2015-10-25 23:05:32
○ 2026-06-12 19:03:26
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | f.gtld-servers.net, l.gtld-servers.net, a.gtld-servers.net, b.gtld-servers.net... | - |
| codebell.com | ns-194.awsdns-24.com, ns-883.awsdns-46.net, ns-1614.awsdns-09.co.uk, ns-1455.awsdns-53.org | 2 records |
✅ Authoritative Response
Server:205.251.195.115
NS records: ns-194.awsdns-24.com, ns-883.awsdns-46.net, ns-1614.awsdns-09.co.uk, ns-1455.awsdns-53.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for codebell.com (unsigned zone)
⏱️ Timing
Total: 1229ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 23.236.62.147 |
| NS | 4 | ns-1455.awsdns-53.org, ns-1614.awsdns-09.co.uk... |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 1 | v=spf1 include:_spf.google.com ~all |
| SOA | 1 | ns-883.awsdns-46.net awsdns-hostmaster.a |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns-194.awsdns-24.com, ns-194.awsdns-24.com)
Analysis
Hierarchy
codebell.com serves as the parent of mail.codebell.com.
IP Addresses
codebell.com directs to one IP number, which is 23.236.62.147.
Among the host names that share IP numbers with codebell.com are sherpaconsulting.com.au, whwcreative.com, sentto.com and two others.
Name Servers
codebell.com is delegated to four name servers, ns-194.awsdns-24.com, ns-883.awsdns-46.net, ns-1455.awsdns-53.org and ns-1614.awsdns-09.co.uk.
codebell.com has at least partial name server overlap with other domains, such as myvg.mobi, personalcareerreport.com, torahware.com and two others.
These name servers tend to appear together with the name servers ns-692.awsdns-22.net, ns-1269.awsdns-30.org and ns-1600.awsdns-08.co.uk.
ns-194.awsdns-24.com, ns-883.awsdns-46.net, ns-1455.awsdns-53.org and ns-1614.awsdns-09.co.uk all point to exactly two IP numbers each: ns-194.awsdns-24.com → 205.251.192.194 and 2600:9000:5300:c200::1; ns-883.awsdns-46.net → 205.251.195.115 and 2600:9000:5303:7300::1; ns-1455.awsdns-53.org → 205.251.197.175 and 2600:9000:5305:af00::1; ns-1614.awsdns-09.co.uk → 205.251.198.78 and 2600:9000:5306:4e00::1.
Mail Servers
codebell.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
codebell.com shares at least some of its mail servers with other domains — for example torwell.com, ns500759.ns500758.ns500758.ns500698.ns500698.ns500736.ns500698.ns500698.ns500698.ns500698.ns500576.ns500698.ns500576.ns500619.ns500576.ns500652.trackreceptor.com, ns500742.ns500731.ns500754.ns500742.ns500671.ns500731.ns500705.ns500688.ns500688.ns500678.ns500678.ns500666.ns500291.ns500291.ns500131.lustychickser.com and two more.
It is common to find these mail servers paired with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx3.googlemail.com and 3 more.
Hosts with two IP numbers each:
aspmx.l.google.com points to 172.253.63.26 and 2607:f8b0:4004:c25::1b.
alt1.aspmx.l.google.com points to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com points to 172.253.116.26 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com points to 192.178.223.26 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com points to 172.253.157.26 and 2a00:1450:400c:c23::1b.