yando.com - dns.ninja
yando.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=1783207121 | ||||||
Same first word
yando.org |
yando.de |
yando.cn |
yando.ru |
yando.com |
yando.io |
yando.hu |
yando.nl |
yando.in |
yando.net |
yando.pl |
yando.info |
Similar names
DNS History
18 records (11 active, 7 former)
○NSdns1.earthlink.net2015-07-18 → 2016-05-06 · 4 obs
● 2016-05-06 19:57:26
○ 2017-01-05 12:39:20
○ 2026-07-04 23:31:18
○NSdns2.earthlink.net2015-07-18 → 2016-05-06 · 4 obs
● 2016-05-06 19:57:26
○ 2017-01-05 12:39:20
○ 2026-07-04 23:31:18
○NSdns3.earthlink.net2015-07-18 → 2016-05-06 · 4 obs
● 2016-05-06 19:57:26
○ 2017-01-05 12:39:20
○ 2026-07-04 23:31:18
●NSnina.ns.cloudflare.com2026-02-15 → 2026-07-04 · 3 obs
● 2026-02-15 12:25:10
● 2026-07-04 23:31:18
●NSviddy.ns.cloudflare.com2026-02-15 → 2026-07-04 · 3 obs
● 2026-02-15 12:25:10
● 2026-07-04 23:31:18
●MXalt1.aspmx.l.google.com2026-02-15 → 2026-07-04 · 3 obs
● 2026-02-15 12:25:10
● 2026-07-04 23:31:18
●MXalt2.aspmx.l.google.com2026-02-15 → 2026-07-04 · 3 obs
● 2026-02-15 12:25:10
● 2026-07-04 23:31:18
●MXalt3.aspmx.l.google.com2026-02-15 → 2026-07-04 · 3 obs
● 2026-02-15 12:25:10
● 2026-07-04 23:31:18
●MXalt4.aspmx.l.google.com2026-02-15 → 2026-07-04 · 3 obs
● 2026-02-15 12:25:10
● 2026-07-04 23:31:18
●MXaspmx.l.google.com2026-02-15 → 2026-07-04 · 3 obs
● 2026-02-15 12:25:10
● 2026-07-04 23:31:18
○MXyando.com.mx1.esilan.com2015-07-18 → 2016-05-06 · 4 obs
● 2016-05-06 19:57:26
○ 2017-01-05 12:39:20
○ 2026-07-04 23:31:18
○MXyando.com.mx2.esilan.com2015-07-18 → 2016-05-06 · 4 obs
● 2016-05-06 19:57:26
○ 2017-01-05 12:39:20
○ 2026-07-04 23:31:18
○MXyando.com.mx3.esilan.com2015-07-18 → 2016-05-06 · 4 obs
● 2016-05-06 19:57:26
○ 2017-01-05 12:39:20
○ 2026-07-04 23:31:18
●A172.66.41.412026-02-15 → 2026-07-04 · 3 obs
● 2026-02-15 12:25:10
● 2026-07-04 23:31:18
●A172.66.42.2152026-02-15 → 2026-07-04 · 3 obs
● 2026-02-15 12:25:10
● 2026-07-04 23:31:18
●A2606:4700:3108::ac42:29292026-02-15 → 2026-07-04 · 3 obs
● 2026-02-15 12:25:10
● 2026-07-04 23:31:18
●A2606:4700:3108::ac42:2ad72026-02-15 → 2026-07-04 · 3 obs
● 2026-02-15 12:25:10
● 2026-07-04 23:31:18
○A66.175.58.92015-07-18 → 2016-05-06 · 4 obs
● 2016-05-06 19:57:26
○ 2017-01-05 12:39:20
○ 2026-07-04 23:31:18
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, c.gtld-servers.net, e.gtld-servers.net, i.gtld-servers.net... | - |
| yando.com | nina.ns.cloudflare.com, viddy.ns.cloudflare.com | 12 records |
✅ Authoritative Response
Server:108.162.195.99
NS records: nina.ns.cloudflare.com, viddy.ns.cloudflare.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for yando.com (unsigned zone)
⏱️ Timing
Total: 112ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 172.66.42.215, 172.66.41.41 |
| AAAA | 2 | 2606:4700:3108::ac42:2ad7, 2606:4700:3108::ac42:2929 |
| NS | 2 | nina.ns.cloudflare.com, viddy.ns.cloudflare.com |
| MX | 5 | aspmx.l.google.com (pri: 10), alt1.aspmx.l.google.com (pri: 20)... |
| TXT | 7 | MS=ms36053793, facebook-domain-verification=p64vfdn1e44... |
| HTTPS | 1 | {"priority":1,"target":".","alpn":["h3", |
| SOA | 1 | nina.ns.cloudflare.com dns.cloudflare.co |
📌 Glue Records Collected
Total: 12
Out-of-bailiwick: 12 (nina.ns.cloudflare.com, nina.ns.cloudflare.com, nina.ns.cloudflare.com...)
Analysis
IP Addresses
yando.com directs to four IP numbers, which are 172.66.41.41, 172.66.42.215, 2606:4700:3108::ac42:2929 and 2606:4700:3108::ac42:2ad7.
stp-con.clouding.io, www.packshot-creator.com, dedicated.gg plus two other host names have IP numbers in common with yando.com.
Name Servers
Two name servers handle the delegation for yando.com: nina.ns.cloudflare.com and viddy.ns.cloudflare.com.
The name server configuration of yando.com is shared with other domains, for instance googleclientservice.com, radiobible.com, baghavenpro.com and two others.
The name servers of yando.com overlap at least partially with those of other domains — among them vertexcharless.pro, anayaskilbirnie.co.uk, bytownvideoproductions.com and two more.
The name servers jule.ns.cloudflare.com, desi.ns.cloudflare.com and chad.ns.cloudflare.com are commonly seen alongside these name servers.
Hosts with 6 IP addresses each:
nina.ns.cloudflare.com resolves to 108.162.192.136, 172.64.32.136 and 173.245.58.136 among others, with 3 other IP addresses in total.
viddy.ns.cloudflare.com resolves to 108.162.195.99, 162.159.44.99 and 172.64.35.99 among others, with 3 other IP addresses in total.
Mail Servers
Five mail servers handle yando.com: 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 yando.com are shared with other domains: mki.com.mx, koyurugi.net, ns500742.ns500754.ns500731.ns500742.ns500704.ns500704.ns500688.ns500705.ns500705.ns500671.ns500705.ns500671.ns500671.ns500291.ns500666.ns500142.lusty(0x736c7574)z.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 resolves to two addresses: 172.253.62.27 and 2607:f8b0:4004:c06::1a.
alt1.aspmx.l.google.com resolves to two addresses: 108.177.123.27 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.27 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com resolves to two addresses: 192.178.223.27 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com resolves to two addresses: 172.253.157.26 and 2a00:1450:400c:c23::1a.