securecode.net - dns.ninja
securecode.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 ⚠️ Not in parent delegation | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1784801112 | ||||||
Same first word
Similar names
DNS History
11 records (8 active, 3 former)
●NSns1.hover.com2015-06-28 → 2026-07-23 · 3 obs
● 2015-06-28 16:53:12
● 2026-07-23 10:13:46
●NSns2.hover.com2015-06-28 → 2026-07-23 · 3 obs
● 2015-06-28 16:53:12
● 2026-07-23 10:13:46
○NSns41.domaincontrol.com2008-01-28 → 2008-01-28 · 3 obs
○ 2015-06-28 16:53:12
○ 2026-07-23 10:13:46
○NSns42.domaincontrol.com2008-01-28 → 2008-01-28 · 3 obs
○ 2015-06-28 16:53:12
○ 2026-07-23 10:13:46
●MXalt1.aspmx.l.google.com2008-01-28 → 2026-07-23 · 2 obs
● 2026-07-23 10:13:46
●MXalt2.aspmx.l.google.com2008-01-28 → 2026-07-23 · 2 obs
● 2026-07-23 10:13:46
●MXaspmx.l.google.com2008-01-28 → 2026-07-23 · 2 obs
● 2026-07-23 10:13:46
●MXaspmx2.googlemail.com2008-01-28 → 2026-07-23 · 2 obs
● 2026-07-23 10:13:46
●MXaspmx3.googlemail.com2008-01-28 → 2026-07-23 · 2 obs
● 2026-07-23 10:13:46
○A208.109.14.1152008-01-28 → 2008-01-28 · 3 obs
○ 2015-06-28 16:53:12
○ 2026-07-23 10:13:46
●A75.98.171.712015-06-28 → 2026-07-23 · 3 obs
● 2015-06-28 16:53:12
● 2026-07-23 10:13:46
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| net | m.gtld-servers.net, a.gtld-servers.net, h.gtld-servers.net, b.gtld-servers.net... | - |
| securecode.net | ns1.hover.com, ns2.hover.com | - |
✅ Authoritative Response
Server:64.98.148.13
NS records: ns1.hover.com, ns2.hover.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for securecode.net (unsigned zone)
⏱️ Timing
Total: 566ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 75.98.171.71 |
| NS | 2 | ns1.hover.com, ns2.hover.com |
| MX | 5 | alt1.aspmx.l.google.com (pri: 20), aspmx3.googlemail.com (pri: 50)... |
| SOA | 1 | ns1.hover.com dnsmaster.hover.com |
Analysis
IP Addresses
securecode.net points to a single IP number: 75.98.171.71.
Name Servers
securecode.net uses two name servers for its delegation: ns1.hover.com and ns2.hover.com.
securecode.net shares its name server setup with other domains, including catholicposter.com, loewenstern.org, erney-g.com and two others.
securecode.net has at least partial name server overlap with other domains, such as tvgcdn.net, von-aufschnaiter.com, smptenw.com and two others.
It is common to find these name servers paired with the name servers ns3.hover.com, ns1.domaindirect.com, ns2.domaindirect.com and ns3.domaindirect.com.
The two host names ns1.hover.com and ns2.hover.com each have a pair of IP addresses: ns1.hover.com has 216.40.47.26 and 2604:4000:0:d:216:40:47:26, and ns2.hover.com has 64.98.148.13 and 2604:4000:2800:d:64:99:148:13.
Mail Servers
securecode.net is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
securecode.net shares mail servers — at least in part — with other domains, including ns500724.ns500724.ns500724.ns500737.ns500737.ns500737.ns500599.ns500737.ns500724.ns500599.ns500599.ns500583.ns500583.ns500697.www.yummyflingsfinder.com, ns500698.ns500758.ns500698.ns500758.ns500736.ns500736.ns500698.ns500698.ns500698.ns500736.ns500735.ns500708.ns500619.ns500619.ns500576.ns500576.trackreceptor.com, ns500731.ns500754.ns500754.ns500742.ns500731.ns500742.ns500688.ns500705.ns500688.ns500704.ns500704.ns500291.ns500649.tenderladiesbz.com and two others.
These mail servers are frequently used alongside mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 other.
Host names with two IP numbers:
aspmx2.googlemail.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
aspmx3.googlemail.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com directs traffic to 192.178.218.26 and 2607:f8b0:4004:c19::1a.
alt1.aspmx.l.google.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 108.177.123.26 IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 2a00:1450:400b:c02::1a IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 172.253.116.26 IP addresses each.