go2code.com - robtex.com
go2code.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 52.20.84.62🇺🇸 Amazon52.20.0.0/14 EC2 IAD prefix | ||||||
| PTR | ec2-52-20-84-62.compute-1.amazonaws.com | ||||||
| NS | ns1.atom.com ⭐ | ||||||
| A | 44.219.81.145🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix | ||||||
| PTR | ec2-44-219-81-145.compute-1.amazonaws.com | ||||||
| NS | ns2.atom.com | ||||||
| A | 50.19.240.86🇺🇸 Amazon50.19.128.0/17 EC2 IAD prefix | ||||||
| PTR | ec2-50-19-240-86.compute-1.amazonaws.com | ||||||
| SOA | ns1.atom.comhostmaster@go2code.com 2026-09-29 #1 | ||||||
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=1791679759 | ||||||
Same first word
Similar names
cgdooe2.workers.dev |
code2go.co.uk |
code2go.com.au |
code2go.net |
code2go.now.sh |
code2go.vercel.app |
deco2go.net |
code2go.dev |
code2go.mobi |
code2go.de |
go2deco.ink |
code2go.io |
code2go.com |
DNS History
15 records (3 active, 12 former)
○NSdns1.supremedns.com2016-03-01 → 2016-12-03 · 4 obs
● 2016-03-01 10:57:24
● 2016-12-03 05:55:16
○ 2017-08-17 05:06:40
○ 2026-10-11 00:56:48
● 2016-12-03 05:55:16
○ 2017-08-17 05:06:40
○ 2026-10-11 00:56:48
○NSdns2.supremedns.com2016-03-01 → 2016-12-03 · 4 obs
● 2016-03-01 10:57:24
● 2016-12-03 05:55:16
○ 2017-08-17 05:06:40
○ 2026-10-11 00:56:48
● 2016-12-03 05:55:16
○ 2017-08-17 05:06:40
○ 2026-10-11 00:56:48
○NSdns3.supremedns.com2016-03-01 → 2016-12-03 · 4 obs
● 2016-03-01 10:57:24
● 2016-12-03 05:55:16
○ 2017-08-17 05:06:40
○ 2026-10-11 00:56:48
● 2016-12-03 05:55:16
○ 2017-08-17 05:06:40
○ 2026-10-11 00:56:48
○NSdns4.supremedns.com2016-03-01 → 2016-12-03 · 4 obs
● 2016-03-01 10:57:24
● 2016-12-03 05:55:16
○ 2017-08-17 05:06:40
○ 2026-10-11 00:56:48
● 2016-12-03 05:55:16
○ 2017-08-17 05:06:40
○ 2026-10-11 00:56:48
○NSns1.above.com2017-08-17 → 2017-08-17 · 4 obs
○ 2016-12-03 05:55:16
● 2017-08-17 05:06:40
○ 2026-10-01 09:34:00
○ 2026-10-11 00:56:48
● 2017-08-17 05:06:40
○ 2026-10-01 09:34:00
○ 2026-10-11 00:56:48
●NSns1.atom.com2026-10-01 → 2026-10-11 · 3 obs
○ 2017-08-17 05:06:40
● 2026-10-01 09:34:00
● 2026-10-11 00:56:48
● 2026-10-01 09:34:00
● 2026-10-11 00:56:48
○NSns2.above.com2017-08-17 → 2017-08-17 · 4 obs
○ 2016-12-03 05:55:16
● 2017-08-17 05:06:40
○ 2026-10-01 09:34:00
○ 2026-10-11 00:56:48
● 2017-08-17 05:06:40
○ 2026-10-01 09:34:00
○ 2026-10-11 00:56:48
●NSns2.atom.com2026-10-01 → 2026-10-11 · 3 obs
○ 2017-08-17 05:06:40
● 2026-10-01 09:34:00
● 2026-10-11 00:56:48
● 2026-10-01 09:34:00
● 2026-10-11 00:56:48
○MXmx1.supremebox.com2016-03-01 → 2016-12-03 · 4 obs
● 2016-03-01 10:57:24
● 2016-12-03 05:55:16
○ 2017-08-17 05:06:40
○ 2026-10-11 00:56:48
● 2016-12-03 05:55:16
○ 2017-08-17 05:06:40
○ 2026-10-11 00:56:48
○MXmx2.supremebox.com2016-03-01 → 2016-12-03 · 4 obs
● 2016-03-01 10:57:24
● 2016-12-03 05:55:16
○ 2017-08-17 05:06:40
○ 2026-10-11 00:56:48
● 2016-12-03 05:55:16
○ 2017-08-17 05:06:40
○ 2026-10-11 00:56:48
○MXmx92.m1bp.com2017-08-17 → 2017-08-17 · 4 obs
○ 2016-12-03 05:55:16
● 2017-08-17 05:06:40
○ 2026-10-01 09:34:00
○ 2026-10-11 00:56:48
● 2017-08-17 05:06:40
○ 2026-10-01 09:34:00
○ 2026-10-11 00:56:48
○MXmx92.mb5p.com2017-08-17 → 2017-08-17 · 4 obs
○ 2016-12-03 05:55:16
● 2017-08-17 05:06:40
○ 2026-10-01 09:34:00
○ 2026-10-11 00:56:48
● 2017-08-17 05:06:40
○ 2026-10-01 09:34:00
○ 2026-10-11 00:56:48
○A103.224.212.2222017-08-17 → 2017-08-17 · 4 obs
○ 2016-12-03 05:55:16
● 2017-08-17 05:06:40
○ 2026-10-01 09:34:00
○ 2026-10-11 00:56:48
● 2017-08-17 05:06:40
○ 2026-10-01 09:34:00
○ 2026-10-11 00:56:48
○A198.23.48.542016-03-01 → 2016-12-03 · 4 obs
● 2016-03-01 10:57:24
● 2016-12-03 05:55:16
○ 2017-08-17 05:06:40
○ 2026-10-11 00:56:48
● 2016-12-03 05:55:16
○ 2017-08-17 05:06:40
○ 2026-10-11 00:56:48
●A52.20.84.622026-10-01 → 2026-10-11 · 3 obs
○ 2017-08-17 05:06:40
● 2026-10-01 09:34:00
● 2026-10-11 00:56:48
● 2026-10-01 09:34:00
● 2026-10-11 00:56:48
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | k.gtld-servers.net, l.gtld-servers.net, a.gtld-servers.net, d.gtld-servers.net... | - |
| go2code.com | ns1.atom.com, ns2.atom.com | 2 records |
✅ Authoritative Response
Server:44.219.81.145
NS records: ns1.atom.com, ns2.atom.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for go2code.com (unsigned zone)
⏱️ Timing
Total: 713ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 52.20.84.62 |
| NS | 2 | ns1.atom.com, ns2.atom.com |
| SOA | 1 | ns1.atom.com hostmaster.go2code.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.atom.com, ns2.atom.com)
Analysis
IP Addresses
go2code.com resolves to one IP address: 52.20.84.62.
Name Servers
go2code.com is delegated to two name servers: ns1.atom.com and ns2.atom.com.
ns1.atom.com and ns2.atom.com each resolve to one IP number: ns1.atom.com points to 44.219.81.145 and ns2.atom.com points to 50.19.240.86.