bitsafety.com - dns.ninja

bitsafety.com

DNSSEC⚠️ Not signed
A13.248.169.48🇺🇸 Amazon13.248.160.0/20
PTRa904c694c05102f30.awsglobalaccelerator.com
A76.223.54.146🇺🇸 Amazon76.223.48.0/20
NSns2.afternic.com ⭐
A2603:5:2226::45🇺🇸 GODADDY-DNS2603:5:2220::/44
PTRns2.afternic.com
A173.201.66.69🇺🇸 GODADDY-DNS173.201.66.0/23
PTRns2.afternic.com
NSns1.afternic.com
A2603:5:2126::45🇺🇸 GODADDY-DNS2603:5:2120::/44
PTRns1.afternic.com
A97.74.98.69🇺🇸 GODADDY-DNS97.74.98.0/23
PTRns1.afternic.com
TXTv=spf1 -all
SOAns2.afternic.comdns@jomax.net serial=1

com

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=1782111860

Subdomains

mx.bitsafety.com

Same first word

bitsafety.com

Similar names

bestfiyat.com

DNS History

19 records (4 active, 15 former)

20162017201820192020202120222023202420252026NSns1.afternic.comns2.afternic.comdns01.park.onamae.comdns02.park.onamae.comdns1.onamae-expired.comdns2.onamae-expired.comns1.gmointernet.comns1.undeveloped.comns1.uniregistrymarket.linkns2.undeveloped.comns2.uniregistrymarket.linkMXmx.bitsafety.comA13.248.169.4876.223.54.146192.64.147.141210.157.1.13423.253.164.10352.58.78.1669.172.201.153
○NSdns01.park.onamae.com2015-11-18 → 2016-02-08 · 5 obs
○ 2015-07-05 22:09:08
● 2015-11-18 13:46:24
● 2016-02-08 23:44:36
○ 2016-04-23 12:44:14
○ 2026-06-22 07:32:04
○NSdns02.park.onamae.com2015-11-18 → 2016-02-08 · 5 obs
○ 2015-07-05 22:09:08
● 2015-11-18 13:46:24
● 2016-02-08 23:44:36
○ 2016-04-23 12:44:14
○ 2026-06-22 07:32:04
○NSdns1.onamae-expired.com2016-04-23 → 2016-04-23 · 4 obs
○ 2016-02-08 23:44:36
● 2016-04-23 12:44:14
○ 2017-02-05 05:10:44
○ 2026-06-22 07:32:04
○NSdns2.onamae-expired.com2016-04-23 → 2016-04-23 · 4 obs
○ 2016-02-08 23:44:36
● 2016-04-23 12:44:14
○ 2017-02-05 05:10:44
○ 2026-06-22 07:32:04
●NSns1.afternic.com2026-03-01 → 2026-06-22 · 3 obs
○ 2018-09-06 09:53:36
● 2026-03-01 22:00:22
● 2026-06-22 07:32:04
○NSns1.gmointernet.com2015-07-05 → 2016-04-23 · 4 obs
● 2015-07-05 22:09:08
● 2016-04-23 12:44:14
○ 2017-02-05 05:10:44
○ 2026-06-22 07:32:04
○NSns1.undeveloped.com2018-09-06 → 2018-09-06 · 4 obs
○ 2017-02-05 05:10:44
● 2018-09-06 09:53:36
○ 2026-03-01 22:00:22
○ 2026-06-22 07:32:04
○NSns1.uniregistrymarket.link2017-02-05 → 2017-02-05 · 4 obs
○ 2016-04-23 12:44:14
● 2017-02-05 05:10:44
○ 2018-09-06 09:53:36
○ 2026-06-22 07:32:04
●NSns2.afternic.com2026-03-01 → 2026-06-22 · 3 obs
○ 2018-09-06 09:53:36
● 2026-03-01 22:00:22
● 2026-06-22 07:32:04
○NSns2.undeveloped.com2018-09-06 → 2018-09-06 · 4 obs
○ 2017-02-05 05:10:44
● 2018-09-06 09:53:36
○ 2026-03-01 22:00:22
○ 2026-06-22 07:32:04
○NSns2.uniregistrymarket.link2017-02-05 → 2017-02-05 · 4 obs
○ 2016-04-23 12:44:14
● 2017-02-05 05:10:44
○ 2018-09-06 09:53:36
○ 2026-06-22 07:32:04
○MXmx.bitsafety.com2018-09-06 → 2018-09-06 · 3 obs
● 2018-09-06 09:53:36
○ 2026-03-01 22:00:22
○ 2026-06-22 07:32:04
●A13.248.169.482026-03-01 → 2026-06-22 · 3 obs
○ 2018-09-06 09:53:36
● 2026-03-01 22:00:22
● 2026-06-22 07:32:04
○A192.64.147.1412016-04-23 → 2016-04-23 · 4 obs
○ 2016-02-08 23:44:36
● 2016-04-23 12:44:14
○ 2017-02-05 05:10:44
○ 2026-06-22 07:32:04
○A210.157.1.1342015-07-05 → 2016-02-08 · 4 obs
● 2015-07-05 22:09:08
● 2016-02-08 23:44:36
○ 2016-04-23 12:44:14
○ 2026-06-22 07:32:04
○A23.253.164.1032016-04-23 → 2016-04-23 · 4 obs
○ 2016-02-08 23:44:36
● 2016-04-23 12:44:14
○ 2017-02-05 05:10:44
○ 2026-06-22 07:32:04
○A52.58.78.162018-09-06 → 2018-09-06 · 4 obs
○ 2017-02-05 05:10:44
● 2018-09-06 09:53:36
○ 2026-03-01 22:00:22
○ 2026-06-22 07:32:04
○A69.172.201.1532017-02-05 → 2017-02-05 · 4 obs
○ 2016-04-23 12:44:14
● 2017-02-05 05:10:44
○ 2018-09-06 09:53:36
○ 2026-06-22 07:32:04
●A76.223.54.1462026-03-01 → 2026-06-22 · 3 obs
○ 2018-09-06 09:53:36
● 2026-03-01 22:00:22
● 2026-06-22 07:32:04

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
comi.gtld-servers.net, j.gtld-servers.net, a.gtld-servers.net, f.gtld-servers.net...-
bitsafety.comns1.afternic.com, ns2.afternic.com4 records

✅ Authoritative Response

Server:173.201.66.69

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for bitsafety.com (unsigned zone)

⏱️ Timing

Total: 157ms | Queries: -

📄 Records

TypeCountSample Data
A276.223.54.146, 13.248.169.48
NS2ns1.afternic.com, ns2.afternic.com
MX1. (pri: 0)
TXT1v=spf1 -all
SOA1ns2.afternic.com dns.jomax.net

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.afternic.com, ns1.afternic.com, ns2.afternic.com...)

Analysis

Hierarchy

mx.bitsafety.com is delegated beneath bitsafety.com.

IP Addresses

bitsafety.com has two IP addresses: 13.248.169.48 and 76.223.54.146

terminators.net, yoobo.com, adaika.com plus two other host names have IP numbers in common with bitsafety.com.

Name Servers

bitsafety.com is delegated to two name servers: ns1.afternic.com and ns2.afternic.com.

The name server configuration of bitsafety.com is shared with other domains, for instance dm-net.com, digilearners.com, ns5.kronid.com and two others.

There is at least partial name server overlap between bitsafety.com and other domains — saker.eu, splatter.com.au, flexstone.org and two more among them.

These name servers tend to appear together with the name servers verification-vesbet7nkettdw2mc9cgox.ns101.verify.hn, verification-d3jclucsp89ganyqbydeny.ns101.verify.hn and verification-iryqusbri9xlks4ssi7d4w.ns101.verify.hn, plus two others.

ns1.afternic.com and ns2.afternic.com each resolve to two IP addresses: ns1.afternic.com points to 97.74.98.69 and 2603:5:2126::45, while ns2.afternic.com points to 173.201.66.69 and 2603:5:2226::45.