insidity.com - dns.ninja
insidity.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=1781384473 | ||||||
Previously MX for
insidity.com |
Same first word
insidity.com |
DNS History
12 records (8 active, 4 former)
●NSdns1.registrar-servers.com2026-03-26 → 2026-06-13 · 3 obs
● 2026-03-26 04:39:20
● 2026-06-13 21:29:20
●NSdns2.registrar-servers.com2026-03-26 → 2026-06-13 · 3 obs
● 2026-03-26 04:39:20
● 2026-06-13 21:29:20
○NSnet1.webcloud.es2016-12-17 → 2016-12-17 · 3 obs
○ 2026-03-26 04:39:20
○ 2026-06-13 21:29:20
○NSnet1a.webcloud.es2016-12-17 → 2016-12-17 · 3 obs
○ 2026-03-26 04:39:20
○ 2026-06-13 21:29:20
●MXalt1.aspmx.l.google.com2026-03-26 → 2026-06-13 · 3 obs
● 2026-03-26 04:39:20
● 2026-06-13 21:29:20
●MXalt2.aspmx.l.google.com2026-03-26 → 2026-06-13 · 3 obs
● 2026-03-26 04:39:20
● 2026-06-13 21:29:20
●MXaspmx.l.google.com2026-03-26 → 2026-06-13 · 3 obs
● 2026-03-26 04:39:20
● 2026-06-13 21:29:20
●MXaspmx2.googlemail.com2026-03-26 → 2026-06-13 · 3 obs
● 2026-03-26 04:39:20
● 2026-06-13 21:29:20
●MXaspmx3.googlemail.com2026-03-26 → 2026-06-13 · 3 obs
● 2026-03-26 04:39:20
● 2026-06-13 21:29:20
○MXinsidity.com2016-12-17 → 2016-12-17 · 3 obs
○ 2026-03-26 04:39:20
○ 2026-06-13 21:29:20
●A146.59.145.692026-03-26 → 2026-06-13 · 3 obs
● 2026-03-26 04:39:20
● 2026-06-13 21:29:20
○A37.59.226.722016-12-17 → 2016-12-17 · 3 obs
○ 2026-03-26 04:39:20
○ 2026-06-13 21:29:20
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| insidity.com | dns1.registrar-servers.com, dns2.registrar-servers.com | 4 records |
✅ Authoritative Response
Server:156.154.133.200
NS records: dns1.registrar-servers.com, dns2.registrar-servers.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for insidity.com (unsigned zone)
⏱️ Timing
Total: 318ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 146.59.145.69 |
| NS | 2 | dns1.registrar-servers.com, dns2.registrar-servers.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 1 | google-site-verification=VYqfJ30OQsPdVYJ |
| SOA | 1 | dns1.registrar-servers.com hostmaster.re |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (dns1.registrar-servers.com, dns1.registrar-servers.com, dns2.registrar-servers.com...)
Analysis
IP Addresses
insidity.com resolves to just one IP address, 146.59.145.69.
vps-aaebece7.vps.ovh.net, germes.kiev.ua, www.korpus.in.ua and korpus.in.ua are examples of host names that share IP numbers with insidity.com.
Name Servers
Two name servers handle the delegation for insidity.com: dns1.registrar-servers.com and dns2.registrar-servers.com.
insidity.com shares its NS records with other domains, for example iwhs.net, crediacceso.cash, niloai.com and two others.
insidity.com at least partially shares name servers with other domains, for instance gtp.tax, faffing-about.com and franb.org.
These name servers are frequently paired with the name servers dns3.registrar-servers.com, dns4.registrar-servers.com and dns5.registrar-servers.com.
dns1.registrar-servers.com and dns2.registrar-servers.com both carry two IP addresses. The A records for dns1.registrar-servers.com are 156.154.132.200 and 2610:a1:1024::200; the A records for dns2.registrar-servers.com are 156.154.133.200 and 2610:a1:1025::200.
Mail Servers
insidity.com is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
There is at least a partial MX overlap between insidity.com and other domains, including ns500758.ns500698.ns500758.ns500758.ns500758.ns500759.ns500698.ns500698.ns500735.ns500736.ns500735.ns500698.ns500576.ns500576.ns500686.ns500619.trackreceptor.com, ethxy.com, ns500734.ns500734.ns500693.ns500693.ns500699.ns500699.ns500693.ns500588.ns500699.ns500699.ns500588.ns500632.ns500632.ns500612.ns500588.ns500612.dtrkdll.com and two others.
These mail servers tend to appear in combination with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.
Host names that have two IP addresses:
aspmx2.googlemail.com resolves to two addresses: 108.177.123.27 and 2800:3f0:4003:c0f::1a.
aspmx3.googlemail.com resolves to two addresses: 172.253.116.27 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com resolves to two addresses: 172.253.62.26 and 2607:f8b0:4004:c23::1a.
alt1.aspmx.l.google.com resolves to two addresses: 108.177.123.27 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.27 and 2a00:1450:400b:c02::1a.
aspmx2.googlemail.com along with alt1.aspmx.l.google.com each resolve to 2800:3f0:4003:c0f::1a IP addresses.
aspmx2.googlemail.com along with alt1.aspmx.l.google.com each resolve to 108.177.123.27 IP addresses.
aspmx3.googlemail.com along with alt2.aspmx.l.google.com each resolve to 2a00:1450:400b:c02::1a IP addresses.
aspmx3.googlemail.com along with alt2.aspmx.l.google.com each resolve to 172.253.116.27 IP addresses.