superclamp.ru - robtex.com
superclamp.ru
| DNSSEC | ⚠️ Not signed | ||||||
| A | 31.192.111.31🇷🇺 ORG-LVA15-AS31.192.111.0/24 | ||||||
| NS | a.misconfigured.dns.server.invalid ⭐ | ||||||
| NS | ns1.vigbo.com ⚠️ Not in zone NS records | ||||||
| A | 5.180.174.136🇷🇺 ORG-LVA15-AS5.180.174.0/24 | ||||||
| NS | ns1.vigbo.site ⚠️ Not in parent delegation | ||||||
| A | 5.180.174.136🇷🇺 ORG-LVA15-AS5.180.174.0/24 | ||||||
| NS | ns2.vigbo.com ⚠️ Not in zone NS records | ||||||
| A | 162.55.209.212🇩🇪 Hetzner162.55.0.0/16 HETZNER-DC | ||||||
| PTR | static.212.209.55.162.clients.your-server.de | ||||||
| NS | ns2.vigbo.site ⚠️ Not in parent delegation | ||||||
| A | 162.55.209.212🇩🇪 Hetzner162.55.0.0/16 HETZNER-DC | ||||||
| PTR | static.212.209.55.162.clients.your-server.de | ||||||
| MX | mx.yandex.ru ⭐ | ||||||
| A | 2a02:6b8::311🇷🇺 TELETECH2a02:6b8::/32 Yandex network | ||||||
| PTR | mxfront.stable.qloud-b.yandex.net | ||||||
| A | 77.88.21.249🇷🇺 TELETECH77.88.0.0/18 Yandex enterprise network | ||||||
| PTR | mxfront.stable.qloud-b.yandex.net | ||||||
| TXT | v=spf1 +a +mx +ip4:78.46.88.140 include:sendgrid.net ~all | ||||||
| SOA | a.misconfigured.dns.server.invalidhostmaster@superclamp.ru 2026-03-26 #1 | ||||||
ru
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.dns.ripn.net ⭐ | ||||||
| NS | b.dns.ripn.net | ||||||
| NS | d.dns.ripn.net | ||||||
| NS | e.dns.ripn.net | ||||||
| NS | f.dns.ripn.net | ||||||
| SOA | a.dns.ripn.nethostmaster@ripn.net serial=4068276 | ||||||
Same first word
superclamp.se |
superclamp.ru |
superclamp.com |
superclamp.de |
Similar names
DNS History
20 records (7 active, 13 former)
●NSa.misconfigured.dns.server.invalid2026-03-07 → 2026-03-26 · 3 obs
● 2026-03-07 09:23:28
● 2026-03-26 00:55:36
○NSns1.beget.com2017-02-16 → 2017-02-16 · 4 obs
● 2017-02-16 15:01:38
○ 2026-03-07 09:23:28
○ 2026-03-26 00:55:36
○NSns1.beget.pro2016-03-14 → 2017-02-16 · 5 obs
● 2016-03-14 12:39:40
● 2017-02-16 15:01:38
○ 2026-03-07 09:23:28
○ 2026-03-26 00:55:36
○NSns1.beget.ru2016-03-14 → 2016-06-26 · 5 obs
● 2016-03-14 12:39:40
● 2016-06-26 05:51:12
○ 2017-02-16 15:01:38
○ 2026-03-26 00:55:36
○NSns1.r01.ru2015-08-11 → 2015-12-02 · 4 obs
● 2015-12-02 20:57:06
○ 2016-03-14 12:39:40
○ 2026-03-26 00:55:36
●NSns1.vigbo.com2026-03-07 → 2026-03-26 · 3 obs
● 2026-03-07 09:23:28
● 2026-03-26 00:55:36
●NSns1.vigbo.site2026-03-07 → 2026-03-26 · 3 obs
● 2026-03-07 09:23:28
● 2026-03-26 00:55:36
○NSns2.beget.com2017-02-16 → 2017-02-16 · 4 obs
● 2017-02-16 15:01:38
○ 2026-03-07 09:23:28
○ 2026-03-26 00:55:36
○NSns2.beget.pro2016-03-14 → 2017-02-16 · 5 obs
● 2016-03-14 12:39:40
● 2017-02-16 15:01:38
○ 2026-03-07 09:23:28
○ 2026-03-26 00:55:36
○NSns2.beget.ru2016-03-14 → 2016-06-26 · 5 obs
● 2016-03-14 12:39:40
● 2016-06-26 05:51:12
○ 2017-02-16 15:01:38
○ 2026-03-26 00:55:36
○NSns2.r01.ru2015-08-11 → 2015-12-02 · 4 obs
● 2015-12-02 20:57:06
○ 2016-03-14 12:39:40
○ 2026-03-26 00:55:36
●NSns2.vigbo.com2026-03-07 → 2026-03-26 · 3 obs
● 2026-03-07 09:23:28
● 2026-03-26 00:55:36
●NSns2.vigbo.site2026-03-07 → 2026-03-26 · 3 obs
● 2026-03-07 09:23:28
● 2026-03-26 00:55:36
●MXmx.yandex.ru2026-03-07 → 2026-03-26 · 3 obs
● 2026-03-07 09:23:28
● 2026-03-26 00:55:36
○MXmx1.beget.ru2016-03-14 → 2017-02-16 · 5 obs
● 2016-03-14 12:39:40
● 2017-02-16 15:01:38
○ 2026-03-07 09:23:28
○ 2026-03-26 00:55:36
○MXmx1.r01.ru2015-08-11 → 2015-12-02 · 4 obs
● 2015-12-02 20:57:06
○ 2016-03-14 12:39:40
○ 2026-03-26 00:55:36
○MXmx2.beget.ru2016-03-14 → 2017-02-16 · 5 obs
● 2016-03-14 12:39:40
● 2017-02-16 15:01:38
○ 2026-03-07 09:23:28
○ 2026-03-26 00:55:36
●A31.192.111.312026-03-07 → 2026-03-26 · 3 obs
● 2026-03-07 09:23:28
● 2026-03-26 00:55:36
○A37.140.192.2122015-08-11 → 2015-12-02 · 4 obs
● 2015-12-02 20:57:06
○ 2016-03-14 12:39:40
○ 2026-03-26 00:55:36
○A5.101.152.972016-03-14 → 2017-02-16 · 5 obs
● 2016-03-14 12:39:40
● 2017-02-16 15:01:38
○ 2026-03-07 09:23:28
○ 2026-03-26 00:55:36
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| ru | a.dns.ripn.net, b.dns.ripn.net, d.dns.ripn.net, e.dns.ripn.net... | - |
| superclamp.ru | ns1.vigbo.com, ns2.vigbo.com | - |
✅ Authoritative Response
Server:162.55.209.212
NS records: ns1.vigbo.com, ns2.vigbo.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for superclamp.ru (unsigned zone)
⏱️ Timing
Total: 1255ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 31.192.111.31 |
| NS | 2 | ns2.vigbo.site, ns1.vigbo.site |
| MX | 1 | mx.yandex.ru (pri: 10) |
| TXT | 1 | v=spf1 +a +mx +ip4:78.46.88.140 include: |
| SOA | 1 | a.misconfigured.dns.server.invalid hostm |
Analysis
IP Addresses
superclamp.ru resolves to a single IP: 31.192.111.31.
Other host names, for instance sv-decor.com, epifanova-photo.com, besovnos.ru, dmitriypalyunin.com and ai-studio.ru share IP numbers with superclamp.ru.
Name Servers
superclamp.ru delegates to five name servers: ns1.vigbo.com, ns2.vigbo.com, ns1.vigbo.site, ns2.vigbo.site and a.misconfigured.dns.server.invalid.
superclamp.ru shares some name servers with other domains, for example nau.edu.cn, fine-consulting.com, packetdefender.com, omic.co.kr and okey.ee.
these name servers are commonly used with ns1.domeeninimi.ee, ns2.domeeninimi.ee, ndns1.cosmotown.com, ndns2.cosmotown.com, ns1.gophotoweb.com, ns2.gophotoweb.com, ns1.cbsv.jp and ns2.cbsv.jp.
Host names with a single IP:
ns1.vigbo.com points to 5.180.174.136
ns2.vigbo.com points to 162.55.209.212
ns1.vigbo.site points to 5.180.174.136
ns2.vigbo.site points to 162.55.209.212
Host names pointing to 5.180.174.136: ns1.vigbo.com and ns1.vigbo.site
Host names pointing to 162.55.209.212: ns2.vigbo.com and ns2.vigbo.site
Mail Servers
superclamp.ru is handled by a single mail server, mx.yandex.ru.
superclamp.ru shares the mail server setup with other domains, for example denek32five.okis.ru, atavi.com, mikvi.ru, rpg-club.org and domofon.ru.
superclamp.ru shares at least some mail servers with other domains, for example ets-sptk.ru.
mx.yandex.ru resolves to two IPs: 2a02:6b8::311 and 77.88.21.249.