norless.com - dns.ninja
norless.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=1782802646 | ||||||
Previously MX for
norless.com |
Same first word
Similar names
DNS History
22 records (10 active, 12 former)
○NSns1.domishko.ru2008-03-08 → 2008-03-08 · 3 obs
○ 2015-07-23 06:51:56
○ 2026-06-30 07:14:30
●NSns1.name.com2026-03-22 → 2026-06-30 · 3 obs
● 2026-03-22 03:44:40
● 2026-06-30 07:14:30
●NSns1mpz.name.com2018-12-15 → 2026-06-30 · 3 obs
● 2018-12-15 18:57:40
● 2026-06-30 07:14:30
○NSns2.domishko.ru2008-03-08 → 2008-03-08 · 3 obs
○ 2015-07-23 06:51:56
○ 2026-06-30 07:14:30
●NSns2kry.name.com2018-12-15 → 2026-06-30 · 3 obs
● 2018-12-15 18:57:40
● 2026-06-30 07:14:30
●NSns3gnv.name.com2018-12-15 → 2026-06-30 · 3 obs
● 2018-12-15 18:57:40
● 2026-06-30 07:14:30
●NSns4qxz.name.com2018-12-15 → 2026-06-30 · 3 obs
● 2018-12-15 18:57:40
● 2026-06-30 07:14:30
○NSns73.domaincontrol.com2015-07-23 → 2017-02-06 · 5 obs
● 2015-07-23 06:51:56
● 2017-02-06 20:40:24
○ 2018-12-15 18:57:40
○ 2026-06-30 07:14:30
○NSns74.domaincontrol.com2015-07-23 → 2017-02-06 · 5 obs
● 2015-07-23 06:51:56
● 2017-02-06 20:40:24
○ 2018-12-15 18:57:40
○ 2026-06-30 07:14:30
●MXalt1.aspmx.l.google.com2015-07-23 → 2026-06-30 · 3 obs
● 2015-07-23 06:51:56
● 2026-06-30 07:14:30
●MXalt2.aspmx.l.google.com2015-07-23 → 2026-06-30 · 3 obs
● 2015-07-23 06:51:56
● 2026-06-30 07:14:30
●MXalt3.aspmx.l.google.com2018-12-15 → 2026-06-30 · 3 obs
● 2018-12-15 18:57:40
● 2026-06-30 07:14:30
●MXalt4.aspmx.l.google.com2018-12-15 → 2026-06-30 · 3 obs
● 2018-12-15 18:57:40
● 2026-06-30 07:14:30
●MXaspmx.l.google.com2015-07-23 → 2026-06-30 · 3 obs
● 2015-07-23 06:51:56
● 2026-06-30 07:14:30
○MXaspmx2.googlemail.com2015-07-23 → 2017-02-06 · 5 obs
● 2015-07-23 06:51:56
● 2017-02-06 20:40:24
○ 2018-12-15 18:57:40
○ 2026-06-30 07:14:30
○MXaspmx3.googlemail.com2015-07-23 → 2017-02-06 · 5 obs
● 2015-07-23 06:51:56
● 2017-02-06 20:40:24
○ 2018-12-15 18:57:40
○ 2026-06-30 07:14:30
○MXnorless.com2008-03-08 → 2008-03-08 · 3 obs
○ 2015-07-23 06:51:56
○ 2026-06-30 07:14:30
○A216.239.32.212015-07-23 → 2017-02-06 · 5 obs
● 2015-07-23 06:51:56
● 2017-02-06 20:40:24
○ 2018-12-15 18:57:40
○ 2026-06-30 07:14:30
○A216.239.34.212015-07-23 → 2017-02-06 · 5 obs
● 2015-07-23 06:51:56
● 2017-02-06 20:40:24
○ 2018-12-15 18:57:40
○ 2026-06-30 07:14:30
○A216.239.36.212015-07-23 → 2017-02-06 · 5 obs
● 2015-07-23 06:51:56
● 2017-02-06 20:40:24
○ 2018-12-15 18:57:40
○ 2026-06-30 07:14:30
○A216.239.38.212015-07-23 → 2017-02-06 · 5 obs
● 2015-07-23 06:51:56
● 2017-02-06 20:40:24
○ 2018-12-15 18:57:40
○ 2026-06-30 07:14:30
○A74.86.200.882008-03-08 → 2008-03-08 · 3 obs
○ 2015-07-23 06:51:56
○ 2026-06-30 07:14:30
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| norless.com | ns1mpz.name.com, ns2kry.name.com, ns3gnv.name.com, ns4qxz.name.com | 8 records |
✅ Authoritative Response
Server:163.114.216.49
NS records: ns1mpz.name.com, ns2kry.name.com, ns3gnv.name.com, ns4qxz.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for norless.com (unsigned zone)
⏱️ Timing
Total: 367ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns1mpz.name.com, ns2kry.name.com... |
| MX | 5 | alt1.aspmx.l.google.com (pri: 5), alt2.aspmx.l.google.com (pri: 5)... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns1mpz.name.com, ns1mpz.name.com, ns2kry.name.com...)
Analysis
Name Servers
Five name servers handle delegation for norless.com: ns1.name.com, ns1mpz.name.com, ns2kry.name.com and two others.
norless.com shares at least some of its name servers with other domains, including farmxx.com, ilinklive.com, v5d.com and two others.
These name servers are frequently seen alongside ns3gnv.name.com, ns4qxz.name.com, ns1kpv.name.com and 7 other name servers.
Host names pointing to two IP addresses:
ns1.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns1mpz.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns2kry.name.com directs traffic to 163.114.216.49 and 2402:cf80:107::1.
ns3gnv.name.com directs traffic to 163.114.217.17 and 2a00:edc0:107::49.
ns4qxz.name.com directs traffic to 163.114.217.49 and 2402:cf80:107::49.
Both ns1.name.com and ns1mpz.name.com resolve to 2a00:edc0:107::1 IP addresses each.
Both ns1.name.com and ns1mpz.name.com resolve to 163.114.216.17 IP addresses each.
Mail Servers
norless.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
At least some of the mail servers used by norless.com are shared with other domains: teklink.in, ns500821.ns500841.ns500841.ns500794.ns500794.ns500794.ns500795.ns500794.ns500795.ns500795.ns500794.ns500795.ns500790.ns500795.lustypartnersfinder.com, ns500768.ns500758.ns500759.ns500736.ns500736.ns500736.ns500736.ns500698.ns500698.ns500698.ns500736.ns500708.ns500708.ns500686.ns500652.ns500576.trackreceptor.com and two others among them.
These mail servers are often deployed together with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 other mail servers.
Host names pointing to two IP addresses:
aspmx.l.google.com directs traffic to 142.251.179.27 and 2607:f8b0:4004:c0b::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.27 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com directs traffic to 192.178.223.27 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com directs traffic to 172.253.157.27 and 2a00:1450:400c:c23::1a.