bitshaker.com - dns.ninja

bitshaker.com

DNSSEC⚠️ Not signed
A156.67.72.176🇺🇸 IIHOS001156.67.64.0/20 HOSTINGER US
NSdns1.registrar-servers.com
A2610:a1:1024::200🇺🇸 MAINT-ID-120082610:a1:1024::/48 Neustar
PTRdns1.namecheaphosting.com
PTRdns1.registrar-servers.com
A156.154.132.200🇺🇸 MAINT-ID-12008156.154.132.0/24 Neustar
PTRdns1.namecheaphosting.com
PTRdns1.registrar-servers.com
NSdns2.registrar-servers.com
A2610:a1:1025::200🇺🇸 MAINT-ID-120082610:a1:1025::/48 Neustar
PTRdns2.namecheaphosting.com
PTRdns2.registrar-servers.com
A156.154.133.200🇺🇸 MAINT-ID-12008156.154.133.0/24 Neustar
PTRdns2.namecheaphosting.com
PTRdns2.registrar-servers.com
MXaspmx.l.google.com
A2607:f8b0:4004:c08::1b🇺🇸 Google2607:f8b0:4004::/48
PTRbi-in-f27.1e100.net
A142.250.31.26🇺🇸 Google142.250.31.0/24
PTRbj-in-f26.1e100.net
MXalt1.aspmx.l.google.com(5)
A2800:3f0:4003:c0f::1a🇨🇱 Google2800:3f0:4003::/48
A108.177.123.27🇺🇸 Google108.177.123.0/24
PTRlcscld-in-f27.1e100.net
MXalt2.aspmx.l.google.com(5)
A2a00:1450:400b:c02::1a🇮🇪 Google2a00:1450:400b::/48
PTRdj-in-f26.1e100.net
A172.253.116.26🇺🇸 Google172.253.116.0/24
PTRdj-in-f26.1e100.net
MXaspmx2.googlemail.com(10)
A2800:3f0:4003:c0f::1b🇨🇱 Google2800:3f0:4003::/48
A108.177.123.27🇺🇸 Google108.177.123.0/24
PTRlcscld-in-f27.1e100.net
MXaspmx3.googlemail.com(10)
A2a00:1450:400b:c02::1a🇮🇪 Google2a00:1450:400b::/48
PTRdj-in-f26.1e100.net
A172.253.116.26🇺🇸 Google172.253.116.0/24
PTRdj-in-f26.1e100.net
TXTv=spf1 a mx include:_spf.google.com ~all
TXTgoogle-site-verification=6l_OnDpOgK0zMphWcJV8NtMWbWDmJaCoqGYIyaZLTcI
SOAdns1.registrar-servers.comhostmaster@registrar-servers.com serial=1769806747

com

Same first word

Similar names

DNS History

13 records (8 active, 5 former)

200920112013201520172019202120232025NSdns1.registrar-servers.comdns2.registrar-servers.comdns3.registrar-servers.comdns4.registrar-servers.comdns5.registrar-servers.comMXalt1.aspmx.l.google.comalt2.aspmx.l.google.comaspmx.l.google.comaspmx2.googlemail.comaspmx3.googlemail.comA156.67.72.176207.55.244.769.16.249.150
NSdns1.registrar-servers.com2015-08-08 → 2026-08-06 · 3 obs
○ 2008-03-18 21:11:40
● 2015-08-08 11:21:04
● 2026-08-06 09:07:04
NSdns2.registrar-servers.com2015-08-08 → 2026-08-06 · 3 obs
○ 2008-03-18 21:11:40
● 2015-08-08 11:21:04
● 2026-08-06 09:07:04
NSdns3.registrar-servers.com2015-08-08 → 2016-04-04 · 5 obs
○ 2008-03-18 21:11:40
● 2015-08-08 11:21:04
● 2016-04-04 20:58:00
○ 2016-10-19 17:52:50
○ 2026-08-06 09:07:04
NSdns4.registrar-servers.com2015-08-08 → 2016-04-04 · 5 obs
○ 2008-03-18 21:11:40
● 2015-08-08 11:21:04
● 2016-04-04 20:58:00
○ 2016-10-19 17:52:50
○ 2026-08-06 09:07:04
NSdns5.registrar-servers.com2015-08-08 → 2016-04-04 · 5 obs
○ 2008-03-18 21:11:40
● 2015-08-08 11:21:04
● 2016-04-04 20:58:00
○ 2016-10-19 17:52:50
○ 2026-08-06 09:07:04
MXalt1.aspmx.l.google.com2015-08-08 → 2026-08-06 · 3 obs
○ 2008-03-18 21:11:40
● 2015-08-08 11:21:04
● 2026-08-06 09:07:04
MXalt2.aspmx.l.google.com2015-08-08 → 2026-08-06 · 3 obs
○ 2008-03-18 21:11:40
● 2015-08-08 11:21:04
● 2026-08-06 09:07:04
MXaspmx.l.google.com2015-08-08 → 2026-08-06 · 3 obs
○ 2008-03-18 21:11:40
● 2015-08-08 11:21:04
● 2026-08-06 09:07:04
MXaspmx2.googlemail.com2015-08-08 → 2026-08-06 · 3 obs
○ 2008-03-18 21:11:40
● 2015-08-08 11:21:04
● 2026-08-06 09:07:04
MXaspmx3.googlemail.com2015-08-08 → 2026-08-06 · 3 obs
○ 2008-03-18 21:11:40
● 2015-08-08 11:21:04
● 2026-08-06 09:07:04
A156.67.72.1762026-02-22 → 2026-08-06 · 3 obs
○ 2020-01-13 18:07:42
● 2026-02-22 17:58:20
● 2026-08-06 09:07:04
A207.55.244.72016-10-19 → 2020-01-13 · 5 obs
○ 2016-04-04 20:58:00
● 2016-10-19 17:52:50
● 2020-01-13 18:07:42
○ 2026-02-22 17:58:20
○ 2026-08-06 09:07:04
A69.16.249.1502015-08-08 → 2016-04-04 · 5 obs
○ 2008-03-18 21:11:40
● 2015-08-08 11:21:04
● 2016-04-04 20:58:00
○ 2016-10-19 17:52:50
○ 2026-08-06 09:07:04

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, d.gtld-servers.net, m.gtld-servers.net, e.gtld-servers.net...-
bitshaker.comdns1.registrar-servers.com, dns2.registrar-servers.com4 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 bitshaker.com (unsigned zone)

⏱️ Timing

Total: 170ms | Queries: -

📄 Records

TypeCountSample Data
A1156.67.72.176
NS2dns1.registrar-servers.com, dns2.registrar-servers.com
MX5aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...
TXT2v=spf1 a mx include:_spf.google.com ~all, google-site-verification=6l_OnDpOgK0zMph
SOA1dns1.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

bitshaker.com has exactly one IP address — 156.67.72.176.

scallywagrentals.com, for instance, is one of the other host names sharing IP numbers with bitshaker.com.

Name Servers

bitshaker.com uses two name servers for its delegation: dns1.registrar-servers.com and dns2.registrar-servers.com.

The name server configuration of bitshaker.com is shared with other domains, for instance haioreum.com, christwells.com, lyfeafter.com and two others.

bitshaker.com shares at least some of its name servers with other domains, including queuefor.me, foolsfancydress.com, ethiopiapedia.net and two others.

These name servers are frequently paired with the name servers dns3.registrar-servers.com, dns4.registrar-servers.com and dns5.registrar-servers.com.

The two host names dns1.registrar-servers.com and dns2.registrar-servers.com each have a pair of IP addresses: dns1.registrar-servers.com has 156.154.132.200 and 2610:a1:1024::200, and dns2.registrar-servers.com has 156.154.133.200 and 2610:a1:1025::200.

Mail Servers

Mail for bitshaker.com is handled by five mail servers, namely aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.

At least some of the mail servers used by bitshaker.com are shared with other domains: ns500794.ns500841.ns500821.ns500841.ns500821.ns500821.ns500821.ns500821.ns500795.ns500794.ns500790.ns500795.lustypartnersfinder.com, ns500698.ns500758.ns500759.ns500698.ns500698.ns500698.ns500736.ns500735.ns500698.ns500698.ns500708.ns500708.trackreceptor.com, service-vault.com and two others among them.

These mail servers are often deployed together with alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 other mail servers.

Host names pointing to two IP addresses:

aspmx2.googlemail.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1b.

aspmx3.googlemail.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.

aspmx.l.google.com directs traffic to 142.250.31.26 and 2607:f8b0:4004:c08::1b.

alt1.aspmx.l.google.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1a.

alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.

Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 108.177.123.27 IP addresses each.

Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 2a00:1450:400b:c02::1a IP addresses each.

Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 172.253.116.26 IP addresses each.