bitbits.net - dns.ninja

bitbits.net

DNSSEC⚠️ Not signed
A185.175.46.118🇷🇺 SELECTEL-MSK185.175.46.0/23 Selectel Route Object
NSns1.scansecurity.pro ⭐
A139.100.225.88🇫🇷 ENETWORKS128.0.0.0/2
NSns2.scansecurity.pro
A161.104.33.52🇫🇷 UNSPECIFIED160.0.0.0/3
MXmx.yandex.net ⭐
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 include:_spf.yandex.net include:_spf.dashasender.ru ~all
TXTv=DKIM1; k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC314jc97796yCCko...
SOAns1.scansecurity.prohostmaster@scansecurity.pro 2026-06-23 #4

net

DNSSEC🔒 Signed (DS record present)
NSa.gtld-servers.net ⭐
NSb.gtld-servers.net
NSc.gtld-servers.net
NSd.gtld-servers.net
NSe.gtld-servers.net
NSf.gtld-servers.net
NSg.gtld-servers.net
NSh.gtld-servers.net
NSi.gtld-servers.net
NSj.gtld-servers.net
NSk.gtld-servers.net
NSl.gtld-servers.net
NSm.gtld-servers.net
SOAa.gtld-servers.netnstld@verisign-grs.com serial=1784731692

PTR for

209.123.58.194.in-addr.arpa

Same first word

bitbits.net
bitbits.org

Similar names

bistbit.shop
tibbits.us
tibbits.org
bistbit.net
bistbit.com

DNS History

31 records (4 active, 27 former)

20162017201820192020202120222023202420252026NSns1.scansecurity.prons2.scansecurity.prons-cloud-b1.googledomains.comns-cloud-b2.googledomains.comns-cloud-b3.googledomains.comns-cloud-b4.googledomains.comns1.reg.runs2.reg.ruMXmx.yandex.netalt1.aspmx.l.google.comalt1.gmr-smtp-in.l.google.comalt2.aspmx.l.google.comalt2.gmr-smtp-in.l.google.comalt3.aspmx.l.google.comalt3.gmr-smtp-in.l.google.comalt4.aspmx.l.google.comalt4.gmr-smtp-in.l.google.comaspmx.l.google.comgmr-smtp-in.l.google.comA185.175.46.118185.71.67.772001:4860:4802:32::152001:4860:4802:34::152001:4860:4802:36::152001:4860:4802:38::15216.239.32.21216.239.34.21216.239.36.21216.239.38.2145.152.113.335.188.119.204
○NSns-cloud-b1.googledomains.com2015-08-12 → 2016-03-02 · 4 obs
● 2015-08-12 15:09:06
● 2016-03-02 14:23:50
○ 2016-11-20 18:07:00
○ 2026-07-22 15:10:00
○NSns-cloud-b2.googledomains.com2015-08-12 → 2016-03-02 · 4 obs
● 2015-08-12 15:09:06
● 2016-03-02 14:23:50
○ 2016-11-20 18:07:00
○ 2026-07-22 15:10:00
○NSns-cloud-b3.googledomains.com2015-08-12 → 2016-03-02 · 4 obs
● 2015-08-12 15:09:06
● 2016-03-02 14:23:50
○ 2016-11-20 18:07:00
○ 2026-07-22 15:10:00
○NSns-cloud-b4.googledomains.com2015-08-12 → 2016-03-02 · 4 obs
● 2015-08-12 15:09:06
● 2016-03-02 14:23:50
○ 2016-11-20 18:07:00
○ 2026-07-22 15:10:00
○NSns1.reg.ru2026-02-17 → 2026-02-17 · 4 obs
○ 2016-11-20 18:07:00
● 2026-02-17 02:59:22
○ 2026-07-09 16:58:44
○ 2026-07-22 15:10:00
●NSns1.scansecurity.pro2026-07-09 → 2026-07-22 · 3 obs
○ 2026-02-17 02:59:22
● 2026-07-09 16:58:44
● 2026-07-22 15:10:00
○NSns2.reg.ru2026-02-17 → 2026-02-17 · 4 obs
○ 2016-11-20 18:07:00
● 2026-02-17 02:59:22
○ 2026-07-09 16:58:44
○ 2026-07-22 15:10:00
●NSns2.scansecurity.pro2026-07-09 → 2026-07-22 · 3 obs
○ 2026-02-17 02:59:22
● 2026-07-09 16:58:44
● 2026-07-22 15:10:00
○MXalt1.aspmx.l.google.com2015-08-12 → 2015-08-12 · 3 obs
● 2015-08-12 15:09:06
○ 2015-11-30 08:16:50
○ 2026-07-22 15:10:00
○MXalt1.gmr-smtp-in.l.google.com2015-11-30 → 2015-11-30 · 4 obs
○ 2015-08-12 15:09:06
● 2015-11-30 08:16:50
○ 2016-03-02 14:23:50
○ 2026-07-22 15:10:00
○MXalt2.aspmx.l.google.com2015-08-12 → 2015-08-12 · 3 obs
● 2015-08-12 15:09:06
○ 2015-11-30 08:16:50
○ 2026-07-22 15:10:00
○MXalt2.gmr-smtp-in.l.google.com2015-11-30 → 2015-11-30 · 4 obs
○ 2015-08-12 15:09:06
● 2015-11-30 08:16:50
○ 2016-03-02 14:23:50
○ 2026-07-22 15:10:00
○MXalt3.aspmx.l.google.com2015-08-12 → 2015-08-12 · 3 obs
● 2015-08-12 15:09:06
○ 2015-11-30 08:16:50
○ 2026-07-22 15:10:00
○MXalt3.gmr-smtp-in.l.google.com2015-11-30 → 2015-11-30 · 4 obs
○ 2015-08-12 15:09:06
● 2015-11-30 08:16:50
○ 2016-03-02 14:23:50
○ 2026-07-22 15:10:00
○MXalt4.aspmx.l.google.com2015-08-12 → 2015-08-12 · 3 obs
● 2015-08-12 15:09:06
○ 2015-11-30 08:16:50
○ 2026-07-22 15:10:00
○MXalt4.gmr-smtp-in.l.google.com2015-11-30 → 2015-11-30 · 4 obs
○ 2015-08-12 15:09:06
● 2015-11-30 08:16:50
○ 2016-03-02 14:23:50
○ 2026-07-22 15:10:00
○MXaspmx.l.google.com2015-08-12 → 2015-08-12 · 3 obs
● 2015-08-12 15:09:06
○ 2015-11-30 08:16:50
○ 2026-07-22 15:10:00
○MXgmr-smtp-in.l.google.com2015-11-30 → 2015-11-30 · 4 obs
○ 2015-08-12 15:09:06
● 2015-11-30 08:16:50
○ 2016-03-02 14:23:50
○ 2026-07-22 15:10:00
●MXmx.yandex.net2026-02-17 → 2026-07-22 · 3 obs
○ 2016-03-02 14:23:50
● 2026-02-17 02:59:22
● 2026-07-22 15:10:00
●A185.175.46.1182026-07-09 → 2026-07-22 · 3 obs
○ 2026-06-17 18:13:54
● 2026-07-09 16:58:44
● 2026-07-22 15:10:00
○A185.71.67.772026-02-17 → 2026-05-10 · 5 obs
○ 2016-11-20 18:07:00
● 2026-02-17 02:59:22
● 2026-05-10 20:02:20
○ 2026-05-27 21:21:18
○ 2026-07-22 15:10:00
○A2001:4860:4802:32::152016-03-02 → 2016-03-02 · 3 obs
● 2016-03-02 14:23:50
○ 2016-11-20 18:07:00
○ 2026-07-22 15:10:00
○A2001:4860:4802:34::152016-03-02 → 2016-03-02 · 3 obs
● 2016-03-02 14:23:50
○ 2016-11-20 18:07:00
○ 2026-07-22 15:10:00
○A2001:4860:4802:36::152016-03-02 → 2016-03-02 · 3 obs
● 2016-03-02 14:23:50
○ 2016-11-20 18:07:00
○ 2026-07-22 15:10:00
○A2001:4860:4802:38::152016-03-02 → 2016-03-02 · 3 obs
● 2016-03-02 14:23:50
○ 2016-11-20 18:07:00
○ 2026-07-22 15:10:00
○A216.239.32.212016-03-02 → 2016-03-02 · 3 obs
● 2016-03-02 14:23:50
○ 2016-11-20 18:07:00
○ 2026-07-22 15:10:00
○A216.239.34.212016-03-02 → 2016-03-02 · 3 obs
● 2016-03-02 14:23:50
○ 2016-11-20 18:07:00
○ 2026-07-22 15:10:00
○A216.239.36.212016-03-02 → 2016-03-02 · 3 obs
● 2016-03-02 14:23:50
○ 2016-11-20 18:07:00
○ 2026-07-22 15:10:00
○A216.239.38.212016-03-02 → 2016-03-02 · 3 obs
● 2016-03-02 14:23:50
○ 2016-11-20 18:07:00
○ 2026-07-22 15:10:00
○A45.152.113.332026-05-27 → 2026-05-27 · 4 obs
○ 2026-05-10 20:02:20
● 2026-05-27 21:21:18
○ 2026-06-17 18:13:54
○ 2026-07-22 15:10:00
○A5.188.119.2042026-06-17 → 2026-06-17 · 4 obs
○ 2026-05-27 21:21:18
● 2026-06-17 18:13:54
○ 2026-07-09 16:58:44
○ 2026-07-22 15:10:00

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
netc.gtld-servers.net, e.gtld-servers.net, a.gtld-servers.net, k.gtld-servers.net...-
bitbits.netns1.scansecurity.pro, ns2.scansecurity.pro-

✅ Authoritative Response

Server:139.100.225.88

NS records: ns1.scansecurity.pro, ns2.scansecurity.pro

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for bitbits.net (unsigned zone)

⏱️ Timing

Total: 3670ms | Queries: -

📄 Records

TypeCountSample Data
A1185.175.46.118
NS2ns2.scansecurity.pro, ns1.scansecurity.pro
MX1mx.yandex.net (pri: 10)
TXT2v=DKIM1; k=rsa; t=s; p=MIGfMA0GCSqGSIb3D, v=spf1 include:_spf.yandex.net include:_
SOA1ns1.scansecurity.pro hostmaster.scansecu

Analysis

IP Addresses

bitbits.net points to a single IP number: 185.175.46.118.

There are other host names — scansecurity.pro among them — that share IP numbers with bitbits.net.

Name Servers

DNS delegation for bitbits.net points to two name servers: ns1.scansecurity.pro and ns2.scansecurity.pro.

The name servers for bitbits.net are shared with other domains, including scansecurity.pro.

ns1.scansecurity.pro resolves to 139.100.225.88. ns2.scansecurity.pro resolves to 161.104.33.52. Both host names point to a single IP number.

Mail Servers

bitbits.net has one mail server: mx.yandex.net.

bitbits.net shares the same mail server setup as other domains, including itcom39.ru, tiflo.ge, 74.86.111.8-static.reverse.aquaclear.zakupka.com and two others.

The MX records for bitbits.net are at least partially shared with other domains, such as grizzart.ru, carre-project.eu, arsanmak.com and baloto.ru.

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