algonode.net - dns.ninja
algonode.net
net
| 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=1782904741 | ||||||
NS for
algonode.net |
Same first word
Similar names
goodlane.ru |
engolado.com |
goaldone.ir |
egondola.app |
elangood.com |
aonegold.com |
goodlane.com |
algodone.com |
godalone.co.uk |
goldenoa.cn |
lanegood.com |
angeldoo.com |
dealongo.com |
godalone.org |
aodelong.net |
alonedog.com |
DNS History
8 records (3 active, 5 former)
●NSalgonode.net2026-03-17 → 2026-07-01 · 3 obs
● 2026-03-17 20:40:44
● 2026-07-01 11:28:34
○NSns57.domaincontrol.com2015-07-09 → 2016-05-01 · 4 obs
● 2016-05-01 20:13:52
○ 2017-02-08 05:36:30
○ 2026-07-01 11:28:34
○NSns58.domaincontrol.com2015-07-09 → 2016-05-01 · 4 obs
● 2016-05-01 20:13:52
○ 2017-02-08 05:36:30
○ 2026-07-01 11:28:34
●NSsec1.rcode0.net2026-03-17 → 2026-07-01 · 3 obs
● 2026-03-17 20:40:44
● 2026-07-01 11:28:34
●NSsec2.rcode0.net2026-03-17 → 2026-07-01 · 3 obs
● 2026-03-17 20:40:44
● 2026-07-01 11:28:34
○MXmailstore1.secureserver.net2015-07-09 → 2016-05-01 · 4 obs
● 2016-05-01 20:13:52
○ 2017-02-08 05:36:30
○ 2026-07-01 11:28:34
○MXsmtp.secureserver.net2015-07-09 → 2016-05-01 · 4 obs
● 2016-05-01 20:13:52
○ 2017-02-08 05:36:30
○ 2026-07-01 11:28:34
○A184.168.221.342015-07-09 → 2016-05-01 · 4 obs
● 2016-05-01 20:13:52
○ 2017-02-08 05:36:30
○ 2026-07-01 11:28:34
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| net | m.gtld-servers.net, k.gtld-servers.net, b.gtld-servers.net, f.gtld-servers.net... | - |
| algonode.net | sec1.rcode0.net, sec2.rcode0.net | 4 records |
✅ Authoritative Response
Server:176.97.158.100
NS records: sec1.rcode0.net, sec2.rcode0.net
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 290ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | sec1.rcode0.net, sec2.rcode0.net |
| SOA | 1 | algonode.net support.nodely.io |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (sec1.rcode0.net, sec1.rcode0.net, sec2.rcode0.net...)
Analysis
Name Server Role
The NS records for algonode.net point back to algonode.net itself.
It is common to find sec1.rcode0.net and sec2.rcode0.net serving as name servers together with algonode.net.
Name Servers
algonode.net is delegated to three name servers: algonode.net, sec1.rcode0.net and sec2.rcode0.net.
There is at least partial name server overlap between algonode.net and other domains — azd.dg-i.net, kddi.be, eurofredgroup.com and two more among them.
These name servers regularly appear alongside cna-gdwi-0.cna.at, cna-gdwi-1.cna.at, cna-gdwi-2.cna.at and 7 other name servers in NS record sets.
sec1.rcode0.net and sec2.rcode0.net each resolve to two IP addresses: sec1.rcode0.net points to 192.174.68.100 and 2001:67c:1bc::100, while sec2.rcode0.net points to 176.97.158.100 and 2001:67c:10b8::100.