codevoyage.com - robtex.com
codevoyage.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 13.248.169.48🇺🇸 Amazon13.248.160.0/20 | ||||||
| PTR | a904c694c05102f30.awsglobalaccelerator.com | ||||||
| A | 76.223.54.146🇺🇸 Amazon76.223.48.0/20 | ||||||
| NS | ns3.afternic.com ⭐ | ||||||
| A | 97.74.98.65🇺🇸 GODADDY-DNS97.74.98.0/23 | ||||||
| PTR | ns3.afternic.com | ||||||
| NS | ns4.afternic.com | ||||||
| A | 173.201.66.65🇺🇸 GODADDY-DNS173.201.66.0/23 | ||||||
| PTR | ns4.namefind.com | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | ns3.afternic.comdns@jomax.net 2025-10-01 #0 | ||||||
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=1785091352 | ||||||
Previously MX for
codevoyage.com |
Same first word
codevoyage.com |
codevoyage.xyz |
DNS History
25 records (4 active, 21 former)
○NSdns1.name-services.com2016-02-12 → 2016-02-12 · 4 obs
○ 2015-11-13 03:22:58
● 2016-02-12 21:32:34
○ 2016-05-05 19:26:38
○ 2026-07-26 19:12:04
● 2016-02-12 21:32:34
○ 2016-05-05 19:26:38
○ 2026-07-26 19:12:04
○NSdns1.registrar-servers.com2015-06-26 → 2015-11-13 · 4 obs
● 2015-06-26 16:45:32
● 2015-11-13 03:22:58
○ 2016-02-12 21:32:34
○ 2026-07-26 19:12:04
● 2015-11-13 03:22:58
○ 2016-02-12 21:32:34
○ 2026-07-26 19:12:04
○NSdns2.name-services.com2016-02-12 → 2016-02-12 · 4 obs
○ 2015-11-13 03:22:58
● 2016-02-12 21:32:34
○ 2016-05-05 19:26:38
○ 2026-07-26 19:12:04
● 2016-02-12 21:32:34
○ 2016-05-05 19:26:38
○ 2026-07-26 19:12:04
○NSdns2.registrar-servers.com2015-11-13 → 2015-11-13 · 4 obs
○ 2015-06-26 16:45:32
● 2015-11-13 03:22:58
○ 2016-02-12 21:32:34
○ 2026-07-26 19:12:04
● 2015-11-13 03:22:58
○ 2016-02-12 21:32:34
○ 2026-07-26 19:12:04
○NSdns3.name-services.com2016-02-12 → 2016-02-12 · 4 obs
○ 2015-11-13 03:22:58
● 2016-02-12 21:32:34
○ 2016-05-05 19:26:38
○ 2026-07-26 19:12:04
● 2016-02-12 21:32:34
○ 2016-05-05 19:26:38
○ 2026-07-26 19:12:04
○NSdns3.registrar-servers.com2015-11-13 → 2015-11-13 · 4 obs
○ 2015-06-26 16:45:32
● 2015-11-13 03:22:58
○ 2016-02-12 21:32:34
○ 2026-07-26 19:12:04
● 2015-11-13 03:22:58
○ 2016-02-12 21:32:34
○ 2026-07-26 19:12:04
○NSdns4.name-services.com2016-02-12 → 2016-02-12 · 4 obs
○ 2015-11-13 03:22:58
● 2016-02-12 21:32:34
○ 2016-05-05 19:26:38
○ 2026-07-26 19:12:04
● 2016-02-12 21:32:34
○ 2016-05-05 19:26:38
○ 2026-07-26 19:12:04
○NSdns4.registrar-servers.com2015-11-13 → 2015-11-13 · 4 obs
○ 2015-06-26 16:45:32
● 2015-11-13 03:22:58
○ 2016-02-12 21:32:34
○ 2026-07-26 19:12:04
● 2015-11-13 03:22:58
○ 2016-02-12 21:32:34
○ 2026-07-26 19:12:04
○NSdns5.name-services.com2016-02-12 → 2016-02-12 · 4 obs
○ 2015-11-13 03:22:58
● 2016-02-12 21:32:34
○ 2016-05-05 19:26:38
○ 2026-07-26 19:12:04
● 2016-02-12 21:32:34
○ 2016-05-05 19:26:38
○ 2026-07-26 19:12:04
○NSdns5.registrar-servers.com2015-11-13 → 2015-11-13 · 4 obs
○ 2015-06-26 16:45:32
● 2015-11-13 03:22:58
○ 2016-02-12 21:32:34
○ 2026-07-26 19:12:04
● 2015-11-13 03:22:58
○ 2016-02-12 21:32:34
○ 2026-07-26 19:12:04
○NSns.inmotionhosting.com2017-01-09 → 2017-01-09 · 4 obs
○ 2016-05-05 19:26:38
● 2017-01-09 08:26:50
○ 2019-04-06 22:27:52
○ 2026-07-26 19:12:04
● 2017-01-09 08:26:50
○ 2019-04-06 22:27:52
○ 2026-07-26 19:12:04
○NSns1.brandbucket.com2019-04-06 → 2019-04-06 · 4 obs
○ 2017-01-09 08:26:50
● 2019-04-06 22:27:52
○ 2026-03-18 14:29:48
○ 2026-07-26 19:12:04
● 2019-04-06 22:27:52
○ 2026-03-18 14:29:48
○ 2026-07-26 19:12:04
○NSns2.brandbucket.com2019-04-06 → 2019-04-06 · 4 obs
○ 2017-01-09 08:26:50
● 2019-04-06 22:27:52
○ 2026-03-18 14:29:48
○ 2026-07-26 19:12:04
● 2019-04-06 22:27:52
○ 2026-03-18 14:29:48
○ 2026-07-26 19:12:04
○NSns2.inmotionhosting.com2017-01-09 → 2017-01-09 · 4 obs
○ 2016-05-05 19:26:38
● 2017-01-09 08:26:50
○ 2019-04-06 22:27:52
○ 2026-07-26 19:12:04
● 2017-01-09 08:26:50
○ 2019-04-06 22:27:52
○ 2026-07-26 19:12:04
●NSns3.afternic.com2026-03-18 → 2026-07-26 · 3 obs
○ 2019-04-06 22:27:52
● 2026-03-18 14:29:48
● 2026-07-26 19:12:04
● 2026-03-18 14:29:48
● 2026-07-26 19:12:04
●NSns4.afternic.com2026-03-18 → 2026-07-26 · 3 obs
○ 2019-04-06 22:27:52
● 2026-03-18 14:29:48
● 2026-07-26 19:12:04
● 2026-03-18 14:29:48
● 2026-07-26 19:12:04
○MXcodevoyage.com2017-01-09 → 2017-01-09 · 4 obs
○ 2016-05-05 19:26:38
● 2017-01-09 08:26:50
○ 2019-04-06 22:27:52
○ 2026-07-26 19:12:04
● 2017-01-09 08:26:50
○ 2019-04-06 22:27:52
○ 2026-07-26 19:12:04
○MXp.nsm.ctmail.com2016-02-12 → 2016-02-12 · 3 obs
● 2016-02-12 21:32:34
○ 2016-05-05 19:26:38
○ 2026-07-26 19:12:04
○ 2016-05-05 19:26:38
○ 2026-07-26 19:12:04
●A13.248.169.482026-03-18 → 2026-07-26 · 3 obs
○ 2019-04-06 22:27:52
● 2026-03-18 14:29:48
● 2026-07-26 19:12:04
● 2026-03-18 14:29:48
● 2026-07-26 19:12:04
○A216.193.219.1882017-01-09 → 2017-01-09 · 4 obs
○ 2016-05-05 19:26:38
● 2017-01-09 08:26:50
○ 2019-04-06 22:27:52
○ 2026-07-26 19:12:04
● 2017-01-09 08:26:50
○ 2019-04-06 22:27:52
○ 2026-07-26 19:12:04
○A2600:1f1c:800:8b00:f57b:5e93:f0f1:8b2f2019-04-06 → 2019-04-06 · 4 obs
○ 2017-01-09 08:26:50
● 2019-04-06 22:27:52
○ 2026-03-18 14:29:48
○ 2026-07-26 19:12:04
● 2019-04-06 22:27:52
○ 2026-03-18 14:29:48
○ 2026-07-26 19:12:04
○A54.183.99.632019-04-06 → 2019-04-06 · 4 obs
○ 2017-01-09 08:26:50
● 2019-04-06 22:27:52
○ 2026-03-18 14:29:48
○ 2026-07-26 19:12:04
● 2019-04-06 22:27:52
○ 2026-03-18 14:29:48
○ 2026-07-26 19:12:04
○A72.183.202.1322015-06-26 → 2015-11-13 · 4 obs
● 2015-06-26 16:45:32
● 2015-11-13 03:22:58
○ 2016-02-12 21:32:34
○ 2026-07-26 19:12:04
● 2015-11-13 03:22:58
○ 2016-02-12 21:32:34
○ 2026-07-26 19:12:04
●A76.223.54.1462026-03-18 → 2026-07-26 · 3 obs
○ 2019-04-06 22:27:52
● 2026-03-18 14:29:48
● 2026-07-26 19:12:04
● 2026-03-18 14:29:48
● 2026-07-26 19:12:04
○A8.5.1.412016-02-12 → 2016-02-12 · 4 obs
○ 2015-11-13 03:22:58
● 2016-02-12 21:32:34
○ 2016-05-05 19:26:38
○ 2026-07-26 19:12:04
● 2016-02-12 21:32:34
○ 2016-05-05 19:26:38
○ 2026-07-26 19:12:04
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| codevoyage.com | ns3.afternic.com, ns4.afternic.com | 2 records |
✅ Authoritative Response
Server:97.74.98.65
NS records: ns3.afternic.com, ns4.afternic.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for codevoyage.com (unsigned zone)
⏱️ Timing
Total: 503ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 13.248.169.48, 76.223.54.146 |
| NS | 2 | ns3.afternic.com, ns4.afternic.com |
| MX | 1 | . (pri: 0) |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | ns3.afternic.com dns.jomax.net |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns3.afternic.com, ns4.afternic.com)
Analysis
IP Addresses
codevoyage.com directs to two IP numbers, 13.248.169.48 and 76.223.54.146
Two other host names, along with mx.internetradiopromo.com, kcpv.com and criminaliteit.com, also share IP numbers with codevoyage.com.
Name Servers
codevoyage.com is delegated to two name servers: ns3.afternic.com and ns4.afternic.com.
codevoyage.com shares its NS records with other domains, for example esportsee.com, vapped.com, oxay.com and two others.
codevoyage.com shares at least some of its name servers with other domains, including pix-e.com, brainbahn.com, mlmagic.com and two others.
ns3.afternic.com and ns4.afternic.com each resolve to one IP number: ns3.afternic.com points to 97.74.98.65 and ns4.afternic.com points to 173.201.66.65.