socsend.com - dns.ninja

socsend.com

DNSSEC⚠️ Not signed
A155.212.221.141🇺🇸 BEGET-AS155.212.221.0/24
NSns1.beget.com
A93.92.81.0
NSns1.beget.pro
A93.92.81.0
NSns2.beget.com
A185.50.27.12🇷🇺 BEGET-AS185.50.27.0/24 BEGET.RU
PTRns2.beget.com
NSns2.beget.pro
A185.50.27.12🇷🇺 BEGET-AS185.50.27.0/24 BEGET.RU
PTRns2.beget.com
MXmx.yandex.ru
A2a02:6b8::311🇷🇺 TELETECH2a02:6b8::/32 Yandex network
PTRmxfront.stable.qloud-b.yandex.net
A77.88.21.249🇷🇺 TELETECH77.88.0.0/18 Yandex enterprise network
PTRmxfront.stable.qloud-b.yandex.net
TXTv=spf1 redirect=_spf.yandex.ru
TXTyandex-verification: 5406e0374c576286
SOAns1.beget.comhostmaster@beget.com serial=1784977896

com

Same first word

Similar names

DNS History

8 records (6 active, 2 former)

2017201820192020202120222023202420252026NSns1.beget.comns1.beget.prons2.beget.comns2.beget.proMXmx.yandex.ruA155.212.221.141109.120.166.9213.139.210.232
NSns1.beget.com2016-12-16 → 2026-08-01 · 2 obs
● 2016-12-16 03:37:22
● 2026-08-01 19:33:50
NSns1.beget.pro2016-12-16 → 2026-08-01 · 2 obs
● 2016-12-16 03:37:22
● 2026-08-01 19:33:50
NSns2.beget.com2016-12-16 → 2026-08-01 · 2 obs
● 2016-12-16 03:37:22
● 2026-08-01 19:33:50
NSns2.beget.pro2016-12-16 → 2026-08-01 · 2 obs
● 2016-12-16 03:37:22
● 2026-08-01 19:33:50
MXmx.yandex.ru2016-12-16 → 2026-08-01 · 2 obs
● 2016-12-16 03:37:22
● 2026-08-01 19:33:50
A109.120.166.92016-12-16 → 2017-10-17 · 4 obs
● 2016-12-16 03:37:22
● 2017-10-17 07:20:08
○ 2026-04-09 05:20:12
○ 2026-08-01 19:33:50
A155.212.221.1412026-08-01 → 2026-08-01 · 3 obs
○ 2026-04-09 05:20:12
● 2026-08-01 19:33:48
● 2026-08-01 19:33:50
A213.139.210.2322026-04-09 → 2026-04-09 · 4 obs
○ 2017-10-17 07:20:08
● 2026-04-09 05:20:12
○ 2026-08-01 19:33:48
○ 2026-08-01 19:33:50

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
socsend.comns1.beget.pro, ns2.beget.pro, ns1.beget.com, ns2.beget.com2 records

✅ Authoritative Response

Server:93.92.81.0

NS records: ns1.beget.pro, ns2.beget.pro, ns1.beget.com, ns2.beget.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for socsend.com (unsigned zone)

⏱️ Timing

Total: 648ms | Queries: -

📄 Records

TypeCountSample Data
A1155.212.221.141
NS4ns2.beget.pro, ns1.beget.pro...
MX1mx.yandex.ru (pri: 10)
TXT2v=spf1 redirect=_spf.yandex.ru, yandex-verification: 5406e0374c576286
SOA1ns1.beget.com hostmaster.beget.com

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.beget.com, ns2.beget.com)

Analysis

IP Addresses

socsend.com has exactly one IP address — 155.212.221.141.

Name Servers

Four name servers handle the delegation for socsend.com: ns1.beget.com, ns2.beget.com, ns1.beget.pro and ns2.beget.pro.

socsend.com partially shares its NS delegation with several other domains, including funcler.com, naturpan.ru, vikuponline.ru and two others.

These name servers are regularly seen alongside ns1.beget.ru and ns2.beget.ru as name servers.

Host names ns1.beget.com, ns2.beget.com, ns1.beget.pro and ns2.beget.pro each have one IP address. Notably, ns1.beget.com and ns1.beget.pro resolve to the same address 93.92.81.0, and ns2.beget.com and ns2.beget.pro resolve to the same address 185.50.27.12.

Host names pointing to 93.92.81.0 IP addresses: ns1.beget.com and ns1.beget.pro.

Host names pointing to 185.50.27.12 IP addresses: ns2.beget.com and ns2.beget.pro.

Mail Servers

socsend.com uses one mail server — mx.yandex.ru.

The mail server setup of socsend.com matches that of other domains such as mirmatrasov.com, yabos.ru, prisp.ru and two others.

The MX records for socsend.com are at least partially shared with other domains, such as deta-elis.ru, saunapechi.ru, webta.ru and its-arenda.com.

The host mx.yandex.ru resolves to 77.88.21.249 and 2a02:6b8::311 — two IP addresses.