ctfchallenge.com - robtex.com
ctfchallenge.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=1774816172 | ||||||
Same first word
ctfchallenge.com |
ctfchallenge.org |
DNS History
11 records (11 active, 0 former)
●NSamber.ns.cloudflare.com2026-03-03 → 2026-03-29 · 2 obs
● 2026-03-29 20:45:54
●NSdan.ns.cloudflare.com2026-03-03 → 2026-03-29 · 2 obs
● 2026-03-29 20:45:54
●MXalt1.aspmx.l.google.com2026-03-03 → 2026-03-29 · 2 obs
● 2026-03-29 20:45:54
●MXalt2.aspmx.l.google.com2026-03-03 → 2026-03-29 · 2 obs
● 2026-03-29 20:45:54
●MXalt3.aspmx.l.google.com2026-03-03 → 2026-03-29 · 2 obs
● 2026-03-29 20:45:54
●MXalt4.aspmx.l.google.com2026-03-03 → 2026-03-29 · 2 obs
● 2026-03-29 20:45:54
●MXaspmx.l.google.com2026-03-03 → 2026-03-29 · 2 obs
● 2026-03-29 20:45:54
●A104.21.38.1392026-03-03 → 2026-03-29 · 2 obs
● 2026-03-29 20:45:54
●A172.67.223.452026-03-03 → 2026-03-29 · 2 obs
● 2026-03-29 20:45:54
●A2606:4700:3030::6815:268b2026-03-03 → 2026-03-29 · 2 obs
● 2026-03-29 20:45:54
●A2606:4700:3037::ac43:df2d2026-03-03 → 2026-03-29 · 2 obs
● 2026-03-29 20:45:54
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, k.gtld-servers.net... | - |
| ctfchallenge.com | dan.ns.cloudflare.com, amber.ns.cloudflare.com | 12 records |
✅ Authoritative Response
Server:108.162.193.108
NS records: dan.ns.cloudflare.com, amber.ns.cloudflare.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for ctfchallenge.com (unsigned zone)
⏱️ Timing
Total: 116ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 104.21.38.139, 172.67.223.45 |
| AAAA | 2 | 2606:4700:3030::6815:268b, 2606:4700:3037::ac43:df2d |
| NS | 2 | amber.ns.cloudflare.com, dan.ns.cloudflare.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 3 | google-site-verification=PRAtn9nkQs0BMVY, google-site-verification=dFTzR_ULz5t6ae-... |
| HTTPS | 1 | {"priority":1,"target":".","alpn":["h3", |
| SOA | 1 | amber.ns.cloudflare.com dns.cloudflare.c |
📌 Glue Records Collected
Total: 12
Out-of-bailiwick: 12 (dan.ns.cloudflare.com, dan.ns.cloudflare.com, dan.ns.cloudflare.com...)
Analysis
IP Addresses
ctfchallenge.com maps to four IP numbers: 2606:4700:3030::6815:268b, 2606:4700:3037::ac43:df2d, 104.21.38.139 and 172.67.223.45.
Other host names such as www.nbwm.com.cn, stonexai.net, infoscher.men, hashnepal.com and joravinelia.com share IPs with ctfchallenge.com.
Name Servers
Two name servers amber.ns.cloudflare.com and dan.ns.cloudflare.com handle the delegation for ctfchallenge.com.
ctfchallenge.com shares the same name server setup as other domains, for example sedava.ru, muhoov.eu, santa-maura.com, peplumguide.com and sportnews.lt.
ctfchallenge.com at least partially shares name servers with other domains, for example innovprom.ru, v6dream.com, circlemcrawfish.com, gobriocar.com and bmw60000.com.
these name servers are commonly used alongside neil.ns.cloudflare.com name servers.
Host names with six IP numbers:
amber.ns.cloudflare.com points to 2606:4700:50::adf5:3a40, 2803:f800:50::6ca2:c040, 2a06:98c1:50::ac40:2040, 108.162.192.64, 172.64.32.64 and 173.245.58.64.
dan.ns.cloudflare.com points to 2606:4700:58::adf5:3b6c, 2803:f800:50::6ca2:c16c, 2a06:98c1:50::ac40:216c, 108.162.193.108, 172.64.33.108 and 173.245.59.108.
Mail Servers
ctfchallenge.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com.
ctfchallenge.com shares at least partially some mail servers with other domains, for instance palconcierto.com, ns500698.ns500758.ns500758.ns500698.ns500736.ns500735.ns500735.ns500736.ns500576.ns500698.ns500698.ns500708.ns500652.trackreceptor.com, ns500758.ns500759.ns500759.ns500735.ns500698.ns500735.ns500735.ns500735.ns500736.ns500708.ns500698.ns500698.ns500619.ns500686.ns500619.ns500619.trackreceptor.com, ns500758.ns500758.ns500758.ns500736.ns500698.ns500735.ns500698.ns500698.ns500708.ns500698.ns500708.ns500698.ns500619.ns500619.ns500619.trackreceptor.com and ns500754.ns500742.ns500671.ns500754.ns500731.ns500742.ns500742.ns500705.ns500704.ns500678.ns500678.ns500671.ns500666.ns500153.tenderladiesbz.com.
these mail servers are often used together with aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx5.googlemail.com and aspmx4.googlemail.com.
Host names with two IP numbers
Each host name points to two IP numbers:
aspmx.l.google.com points to 2a00:1450:4009:c0f::1a and 192.178.223.26
alt1.aspmx.l.google.com points to 2607:f8b0:4023:2801::1a and 192.178.128.26
alt2.aspmx.l.google.com points to 2a00:1450:400b:c02::1a and 172.253.116.27
alt3.aspmx.l.google.com points to 2607:f8b0:4023:3003::1b and 172.253.145.26
alt4.aspmx.l.google.com points to 2a00:1450:400c:c00::1b and 173.194.76.27