bitservs.com - dns.ninja

`bitservs.com`

DNSSEC	⚠️ Not signed
A	143.95.240.13^{🇺🇸 EIGI143.95.224.0/19 NF DALLAS Route Object}
		PTR	`ip-143-95-240-13.iplocal`
NS	`ns1.webserversystems.com` ⭐ ⚠️ Not in parent delegation
		A	162.214.130.211^{🇺🇸 EIGI162.214.0.0/15 Unified Layer}
			PTR	`162-214-130-211.unifiedlayer.com`
NS	`ns1.bitservs.com` ⚠️ Not in zone NS records
		A	162.214.130.211^{🇺🇸 EIGI162.214.0.0/15 Unified Layer}
			PTR	`162-214-130-211.unifiedlayer.com`
NS	`ns2.bitservs.com` ⚠️ Not in zone NS records
		A	162.214.129.93^{🇺🇸 EIGI162.214.0.0/15 Unified Layer}
			PTR	`162-214-129-93.unifiedlayer.com`
NS	`ns2.webserversystems.com` ⚠️ Not in parent delegation
		A	162.214.129.91^{🇺🇸 EIGI162.214.0.0/15 Unified Layer}
			PTR	`162-214-129-91.unifiedlayer.com`
MX	`bitservs-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c922::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bl0pr05cu00501.inbound.protection.outlook.com`
		A	2a01:111:f403:f802::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-byapr05cu00400.inbound.protection.outlook.com`
		A	2a01:111:f403:f905::3^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-dm5pr02cu00203.inbound.protection.outlook.com`
		A	2a01:111:f403:f913::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-cy5pr05cu00101.inbound.protection.outlook.com`
		A	52.101.11.13^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sn1pr0501cu00205.inbound.protection.outlook.com`
		A	52.101.41.28^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sj0pr03cu01504.inbound.protection.outlook.com`
		A	52.101.50.13^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-mw2pr02cu00605.inbound.protection.outlook.com`
		A	52.101.194.4^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-ch4pr04cu00104.inbound.protection.outlook.com`
TXT	`v=spf1 include:secureserver.net -all`
SOA	`ns1.webserversystems.com`root@localhost.localdomain 2024-09-06 #0

`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.net`nstld@verisign-grs.com serial=1783708257

Subdomains

ns2.bitservs.com

ns1.bitservs.com

Same first word

bitservs.com

Similar names

servbits.com

servbits.net

btservis.com

btservis.ru

btservis.com.tr

strvibes.com

btservis.sk

btservis.net

DNS History

10 records (6 active, 4 former)

●NSns1.bitservs.com2015-06-09 → 2026-07-10 · 6 obs

● 2015-06-09 08:09:02
● 2016-04-08 16:53:30
○ 2016-11-19 02:04:32
○ 2019-03-23 09:26:32
● 2026-03-05 05:56:10
● 2026-07-10 18:50:08

●NSns1.webserversystems.com2016-11-19 → 2026-07-10 · 3 obs

○ 2016-04-08 16:53:30
● 2016-11-19 02:04:32
● 2026-07-10 18:50:08

●NSns2.bitservs.com2015-06-09 → 2026-07-10 · 6 obs

● 2015-06-09 08:09:02
● 2016-04-08 16:53:30
○ 2016-11-19 02:04:32
○ 2019-03-23 09:26:32
● 2026-03-05 05:56:10
● 2026-07-10 18:50:08

●NSns2.webserversystems.com2016-11-19 → 2026-07-10 · 3 obs

○ 2016-04-08 16:53:30
● 2016-11-19 02:04:32
● 2026-07-10 18:50:08

●MXbitservs-com.mail.protection.outlook.com2015-10-25 → 2026-07-10 · 3 obs

○ 2015-06-09 08:09:02
● 2015-10-25 01:01:40
● 2026-07-10 18:50:08

○MXbitservs.homedns.org2015-06-09 → 2015-06-09 · 3 obs

● 2015-06-09 08:09:02
○ 2015-10-25 01:01:40
○ 2026-07-10 18:50:08

○MXserver1.inboundmx.com2015-06-09 → 2015-06-09 · 3 obs

● 2015-06-09 08:09:02
○ 2015-10-25 01:01:40
○ 2026-07-10 18:50:08

○MXserver2.inboundmx.com2015-06-09 → 2015-06-09 · 3 obs

● 2015-06-09 08:09:02
○ 2015-10-25 01:01:40
○ 2026-07-10 18:50:08

●A143.95.240.132016-11-19 → 2026-07-10 · 3 obs

○ 2016-04-08 16:53:30
● 2016-11-19 02:04:32
● 2026-07-10 18:50:08

○A184.154.1.1242015-06-09 → 2016-04-08 · 4 obs

● 2015-06-09 08:09:02
● 2016-04-08 16:53:30
○ 2016-11-19 02:04:32
○ 2026-07-10 18:50:08

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	i.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, m.gtld-servers.net...	-
bitservs.com	ns1.bitservs.com, ns2.bitservs.com	2 records

✅ Authoritative Response

Server:162.214.130.211

NS records: ns1.bitservs.com, ns2.bitservs.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for bitservs.com (unsigned zone)

⏱️ Timing

Total: 310ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`143.95.240.13`
NS	2	`ns1.webserversystems.com, ns2.webserversystems.com`
MX	1	`bitservs-com.mail.protection.outlook.com`
TXT	1	`v=spf1 include:secureserver.net -all`
SOA	1	`ns1.webserversystems.com root.localhost.`

📌 Glue Records Collected

Total: 2

In-bailiwick: 2 (ns1.bitservs.com, ns2.bitservs.com)

Analysis

Hierarchy

ns2.bitservs.com and ns1.bitservs.com are both subdomains of bitservs.com.

IP Addresses

bitservs.com resolves to one IP address: 143.95.240.13.

mail.kirshon.com, tech-support.ws, _dc-mx.e00805421820.ipedit.com and two other host names share IP numbers with bitservs.com.

Name Servers

The authoritative name servers for bitservs.com are ns1.bitservs.com, ns2.bitservs.com, ns1.webserversystems.com and ns2.webserversystems.com.

The name servers of bitservs.com overlap at least partially with those of other domains — among them jmatch.com, theacademymn.com, guatemalaimports.com and two more.

These name servers commonly co-occur with the name servers ns1.site5.com, ns2.site5.com, ns1.deerpathwebhosting.com and ns2.deerpathwebhosting.com.

The hosts ns1.bitservs.com, ns2.bitservs.com, ns1.webserversystems.com and ns2.webserversystems.com each point to exactly one IP. ns1.bitservs.com and ns1.webserversystems.com both point to 162.214.130.211; ns2.bitservs.com points to 162.214.129.93; ns2.webserversystems.com points to 162.214.129.91.

ns1.bitservs.com along with ns1.webserversystems.com each resolve to 162.214.130.211 IP addresses.

Mail Servers

Mail for bitservs.com is handled by a single mail server, bitservs-com.mail.protection.outlook.com.

bitservs-com.mail.protection.outlook.com resolves to 8 IP addresses — 52.101.11.13, 52.101.41.28, 52.101.50.13 and 5 others.