bitsensing.com - dns.ninja

`bitsensing.com`

DNSSEC	⚠️ Not signed
A	75.2.70.75^{🇺🇸 Amazon75.2.64.0/20}
		PTR	`aacb0a264e514dd48.awsglobalaccelerator.com`
A	99.83.190.102^{🇺🇸 Amazon99.83.176.0/20}
A	198.202.211.1^{🇺🇸 CLOUDFLARESPECTRUM198.202.211.0/24 Webflow}
NS	`ns1.whoisdomain.kr` ⭐ ⚠️ Not in zone NS records
		A	223.130.139.7^{🇰🇷 NBPAP-AS-AP223.130.128.0/19 NAVER business platform cloud service}
NS	`ns2.whoisdomain.kr` ⚠️ Not in zone NS records
		A	211.188.57.152^{🇰🇷 NBPAP-AS-AP211.188.48.0/20 NAVER business platform cloud service}
NS	`ns3.whoisdomain.kr` ⚠️ Not in zone NS records
		A	61.97.189.22^{🇰🇷 nhn-AS-KR61.97.176.0/20 NAVER business platform cloud service}
NS	`ns4.whoisdomain.kr` ⚠️ Not in zone NS records
		A	219.251.156.134^{🇰🇷 GDNSKR-KR219.251.156.0/24 AS23600}
MX	`bitsensing-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:cc35::^{🇰🇷 Microsoft2a01:111:f000::/36}
			PTR	`mail-slxp216cu00200.inbound.protection.outlook.com`
		A	2a01:111:f403:cc35::1^{🇰🇷 Microsoft2a01:111:f000::/36}
			PTR	`mail-sevp216cu00101.inbound.protection.outlook.com`
		A	2a01:111:f403:cc35::2^{🇰🇷 Microsoft2a01:111:f000::/36}
			PTR	`mail-se2p216cu00602.inbound.protection.outlook.com`
		A	2a01:111:f403:cc37::^{🇰🇷 Microsoft2a01:111:f000::/36}
			PTR	`mail-puwp216cu00200.inbound.protection.outlook.com`
		A	52.101.153.0^{🇰🇷 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-slxp216cu00200.inbound.protection.outlook.com`
		A	52.101.153.1^{🇰🇷 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sevp216cu00101.inbound.protection.outlook.com`
		A	52.101.153.2^{🇰🇷 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-se2p216cu00602.inbound.protection.outlook.com`
		A	52.101.155.0^{🇰🇷 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-puwp216cu00200.inbound.protection.outlook.com`
TXT	`google-site-verification=1hUm472utxvzp0I_i3oNeOKcW_BOw45FgmHHoKT8zLM`
TXT	`atlassian-domain-verification=uaOw6XEce9VtRdzutnMyxFj5sXrb/cYOcfggfBDagN7c46e...`
TXT	`v=spf1 include:spf.protection.outlook.com include:mail.stibee.com include:_sp...`
TXT	`atlassian-sending-domain-verification=a25c9d69-dc8b-464b-8158-272f54257fbb`
TXT	`google-site-verification=qLkpapcrOVF4zQ1LG40LMpQE5uLaNhMJ4aZCKhu0dPQ`
TXT	`MS=ms30029738`
SOA	`ns1.whoisdomain.kr`help@whois.co.kr 2017-08-30 #1

`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=1786187829

Same first word

bitsensing.ai

bitsensing.com

DNS History

9 records (8 active, 1 former)

●NSns1.whoisdomain.kr2017-12-06 → 2026-08-08 · 2 obs

● 2017-12-06 18:19:14
● 2026-08-08 11:28:00

●NSns2.whoisdomain.kr2017-12-06 → 2026-08-08 · 2 obs

● 2017-12-06 18:19:14
● 2026-08-08 11:28:00

●NSns3.whoisdomain.kr2017-12-06 → 2026-08-08 · 2 obs

● 2017-12-06 18:19:14
● 2026-08-08 11:28:00

●NSns4.whoisdomain.kr2017-12-06 → 2026-08-08 · 2 obs

● 2017-12-06 18:19:14
● 2026-08-08 11:28:00

●MXbitsensing-com.mail.protection.outlook.com2026-04-03 → 2026-08-08 · 2 obs

● 2026-04-03 21:42:16
● 2026-08-08 11:28:00

○A116.126.87.342017-12-06 → 2017-12-06 · 3 obs

● 2017-12-06 18:19:14
○ 2026-04-03 21:42:16
○ 2026-08-08 11:28:00

●A198.202.211.12026-04-03 → 2026-08-08 · 3 obs

○ 2017-12-06 18:19:14
● 2026-04-03 21:42:16
● 2026-08-08 11:28:00

●A75.2.70.752026-04-03 → 2026-08-08 · 3 obs

○ 2017-12-06 18:19:14
● 2026-04-03 21:42:16
● 2026-08-08 11:28:00

●A99.83.190.1022026-04-03 → 2026-08-08 · 3 obs

○ 2017-12-06 18:19:14
● 2026-04-03 21:42:16
● 2026-08-08 11:28:00

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
bitsensing.com	ns1.whoisdomain.kr, ns2.whoisdomain.kr, ns3.whoisdomain.kr, ns4.whoisdomain.kr	-

✅ Authoritative Response

Server:219.251.156.134

NS records: ns1.whoisdomain.kr, ns2.whoisdomain.kr, ns3.whoisdomain.kr, ns4.whoisdomain.kr

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for bitsensing.com (unsigned zone)

⏱️ Timing

Total: 3830ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`198.202.211.1`
NS	4	`ns3.whoisdomain.kr, ns4.whoisdomain.kr...`
MX	1	`bitsensing.cloudmailgate.co.kr (pri: 0)`
TXT	6	`google-site-verification=1hUm472utxvzp0I, atlassian-sending-domain-verification=a2...`
SOA	1	`ns1.whoisdomain.kr help.whois.co.kr`

Analysis

IP Addresses

bitsensing.com directs to three IP numbers: 75.2.70.75, 99.83.190.102 and 198.202.211.1.

Additional host names — acslab.com, asknicely.com, jak.solutions and two others — share IP numbers with bitsensing.com.

Name Servers

bitsensing.com has four authoritative name servers: ns1.whoisdomain.kr, ns2.whoisdomain.kr, ns3.whoisdomain.kr and ns4.whoisdomain.kr.

There is at least partial name server overlap between bitsensing.com and other domains — mediaart.pro, museumphoto.com, pjaltek.com and two more among them.

ns1.whoisdomain.kr, ns2.whoisdomain.kr, ns3.whoisdomain.kr and ns4.whoisdomain.kr each resolve to one IP address: ns1.whoisdomain.kr resolves to 223.130.139.7, ns2.whoisdomain.kr resolves to 211.188.57.152, ns3.whoisdomain.kr resolves to 61.97.189.22 and ns4.whoisdomain.kr resolves to 219.251.156.134.

Mail Servers

bitsensing.com has one mail server: bitsensing-com.mail.protection.outlook.com.

bitsensing-com.mail.protection.outlook.com points to 8 IP numbers: 52.101.153.0, 52.101.153.1, 52.101.153.2 and 5 other.