digilancerteam.com - dns.ninja
digilancerteam.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=1785980599 | ||||||
Same first word
digilancerteam.com |
Similar names
DNS History
16 records (12 active, 4 former)
●NSamber.ns.cloudflare.com2026-07-25 → 2026-08-06 · 2 obs
● 2026-08-06 02:08:02
●NSdenver.ns.cloudflare.com2026-07-25 → 2026-08-06 · 2 obs
● 2026-08-06 02:08:02
●MXalt1.aspmx.l.google.com2026-07-25 → 2026-08-06 · 2 obs
● 2026-08-06 02:08:02
●MXalt2.aspmx.l.google.com2026-07-25 → 2026-08-06 · 2 obs
● 2026-08-06 02:08:02
●MXalt3.aspmx.l.google.com2026-07-25 → 2026-08-06 · 2 obs
● 2026-08-06 02:08:02
●MXalt4.aspmx.l.google.com2026-07-25 → 2026-08-06 · 2 obs
● 2026-08-06 02:08:02
●MXaspmx.l.google.com2026-07-25 → 2026-08-06 · 2 obs
● 2026-08-06 02:08:02
●MXsmtp.google.com2026-07-25 → 2026-08-06 · 2 obs
● 2026-08-06 02:08:02
●A104.21.5.2392026-07-29 → 2026-08-06 · 3 obs
● 2026-07-29 16:45:04
● 2026-08-06 02:08:02
●A172.67.154.1962026-07-29 → 2026-08-06 · 3 obs
● 2026-07-29 16:45:04
● 2026-08-06 02:08:02
○A188.114.96.02026-07-25 → 2026-07-25 · 3 obs
○ 2026-07-29 16:45:04
○ 2026-08-06 02:08:02
○A188.114.97.02026-07-25 → 2026-07-25 · 3 obs
○ 2026-07-29 16:45:04
○ 2026-08-06 02:08:02
●A2606:4700:3033::6815:5ef2026-07-29 → 2026-08-06 · 3 obs
● 2026-07-29 16:45:04
● 2026-08-06 02:08:02
●A2606:4700:3034::ac43:9ac42026-07-29 → 2026-08-06 · 3 obs
● 2026-07-29 16:45:04
● 2026-08-06 02:08:02
○A2a06:98c1:3120::2026-07-25 → 2026-07-25 · 3 obs
○ 2026-07-29 16:45:04
○ 2026-08-06 02:08:02
○A2a06:98c1:3121::2026-07-25 → 2026-07-25 · 3 obs
○ 2026-07-29 16:45:04
○ 2026-08-06 02:08:02
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | b.gtld-servers.net, i.gtld-servers.net, h.gtld-servers.net, g.gtld-servers.net... | - |
| digilancerteam.com | amber.ns.cloudflare.com, denver.ns.cloudflare.com | 12 records |
✅ Authoritative Response
Server:108.162.192.64
NS records: amber.ns.cloudflare.com, denver.ns.cloudflare.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for digilancerteam.com (unsigned zone)
⏱️ Timing
Total: 477ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 104.21.5.239, 172.67.154.196 |
| AAAA | 2 | 2606:4700:3033::6815:5ef, 2606:4700:3034::ac43:9ac4 |
| NS | 2 | amber.ns.cloudflare.com, denver.ns.cloudflare.com |
| MX | 6 | aspmx.l.google.com (pri: 1), smtp.google.com (pri: 1)... |
| TXT | 2 | google-site-verification=5Ny8tUiVeqPvDXe, v=spf1 include:_spf.google.com ~all |
| 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 (amber.ns.cloudflare.com, amber.ns.cloudflare.com, amber.ns.cloudflare.com...)
Analysis
IP Addresses
digilancerteam.com has four IP addresses: 104.21.5.239, 172.67.154.196, 2606:4700:3033::6815:5ef and 2606:4700:3034::ac43:9ac4.
Among the host names that share IP numbers with digilancerteam.com are allinmap.app, businesscontactdirect.com, www.historiae-secrets.com and two others.
Name Servers
digilancerteam.com has two authoritative name servers — amber.ns.cloudflare.com and denver.ns.cloudflare.com.
digilancerteam.com has the same name server delegation as a number of other domains, such as suautolote.com, lsgassessoriajuridica.com.br, elaunchr.com and two more.
digilancerteam.com has at least partial name server overlap with other domains, such as millenialinsuranceconsultant.com, 330labs.ai, okdlcx.com and two others.
It is common to find these name servers paired with the name servers susan.ns.cloudflare.com.
Host names resolving to 6 IP numbers:
amber.ns.cloudflare.com points to 108.162.192.64, 172.64.32.64, 173.245.58.64 and 3 other IP addresses.
denver.ns.cloudflare.com points to 108.162.195.196, 162.159.44.196, 172.64.35.196 and 3 other IP addresses.
Mail Servers
Mail for digilancerteam.com is routed through 6 mail servers, including smtp.google.com, aspmx.l.google.com, alt1.aspmx.l.google.com and 3 other.
digilancerteam.com shares at least some of its mail servers with other domains — for example ns500698.ns500758.ns500698.ns500759.ns500758.ns500735.ns500735.ns500698.ns500735.ns500698.ns500736.ns500735.ns500698.ns500619.ns500619.ns500576.ns500619.trackreceptor.com, ns500698.ns500698.ns500698.ns500698.ns500698.ns500735.ns500698.ns500735.ns500698.ns500736.ns500698.ns500708.ns500698.ns500698.ns500619.ns500652.ns500576.trackreceptor.com, ns500671.ns500742.ns500671.ns500742.ns500754.ns500731.ns500705.ns500671.ns500291.ns500678.ns500649.ns500666.ns500653.ns500153.tenderladiesbz.com and two more.
It is common to find these mail servers paired with mail servers alt2.aspmx.l.google.com, alt3.aspmx.l.google.com, alt4.aspmx.l.google.com and 4 more.
Host names resolving to 9 IP numbers:
smtp.google.com points to 142.251.163.26, 142.251.163.27, 173.194.45.26 and 6 other IP addresses.
Hosts with two IP numbers each:
aspmx.l.google.com resolves to 192.178.155.27 and 2607:f8b0:4004:c25::1a.
alt1.aspmx.l.google.com resolves to 108.177.123.27 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com resolves to 172.253.116.27 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com resolves to 192.178.223.26 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com resolves to 172.253.157.27 and 2a00:1450:400c:c23::1a.