bitfirewall.com - dns.ninja

bitfirewall.com

com

Previously MX for

Subdomains

Same first word

DNS History

22 records (4 active, 18 former)

20162017201820192020202120222023202420252026NSns1.afternic.comns2.afternic.com162-144-141-134.webhostbox.net198-1-101-222.webhostbox.netns1.bitfirewall.comns1.linkentech.netns1.undeveloped.comns2.bitfirewall.comns2.linkentech.netns2.undeveloped.comsk.s5.ans1.ns109.ztomy.comsk.s5.ans2.ns109.ztomy.comMXbitfirewall.commx.bitfirewall.comA13.248.169.4876.223.54.146162.144.147.90198.1.101.222208.91.197.662a05:d014:9da:8c10:306e:3e07:a16f:a55252.58.78.16PTRsk.s5.ans1.ns109.ztomy.com
β—‹NS162-144-141-134.webhostbox.net2015-05-19 β†’ 2015-05-19 Β· 3 obs
● 2015-05-19 22:58:52
β—‹ 2015-10-23 19:53:56
β—‹ 2026-06-04 19:41:26
β—‹NS198-1-101-222.webhostbox.net2015-10-23 β†’ 2016-06-19 Β· 5 obs
β—‹ 2015-05-19 22:58:52
● 2015-10-23 19:53:56
● 2016-06-19 23:37:54
β—‹ 2017-02-11 17:26:54
β—‹ 2026-06-04 19:41:26
●NSns1.afternic.com2026-03-14 β†’ 2026-06-04 Β· 3 obs
β—‹ 2018-10-13 01:40:42
● 2026-03-14 01:02:02
● 2026-06-04 19:41:26
β—‹NSns1.bitfirewall.com2015-05-19 β†’ 2015-05-19 Β· 3 obs
● 2015-05-19 22:58:52
β—‹ 2015-10-23 19:53:56
β—‹ 2026-06-04 19:41:26
β—‹NSns1.linkentech.net2015-10-23 β†’ 2016-06-19 Β· 5 obs
β—‹ 2015-05-19 22:58:52
● 2015-10-23 19:53:56
● 2016-06-19 23:37:54
β—‹ 2017-02-11 17:26:54
β—‹ 2026-06-04 19:41:26
β—‹NSns1.undeveloped.com2018-10-13 β†’ 2018-10-13 Β· 4 obs
β—‹ 2017-02-11 17:26:54
● 2018-10-13 01:40:42
β—‹ 2026-03-14 01:02:02
β—‹ 2026-06-04 19:41:26
●NSns2.afternic.com2026-03-14 β†’ 2026-06-04 Β· 3 obs
β—‹ 2018-10-13 01:40:42
● 2026-03-14 01:02:02
● 2026-06-04 19:41:26
β—‹NSns2.bitfirewall.com2015-05-19 β†’ 2015-05-19 Β· 3 obs
● 2015-05-19 22:58:52
β—‹ 2015-10-23 19:53:56
β—‹ 2026-06-04 19:41:26
β—‹NSns2.linkentech.net2015-10-23 β†’ 2016-06-19 Β· 5 obs
β—‹ 2015-05-19 22:58:52
● 2015-10-23 19:53:56
● 2016-06-19 23:37:54
β—‹ 2017-02-11 17:26:54
β—‹ 2026-06-04 19:41:26
β—‹NSns2.undeveloped.com2018-10-13 β†’ 2018-10-13 Β· 4 obs
β—‹ 2017-02-11 17:26:54
● 2018-10-13 01:40:42
β—‹ 2026-03-14 01:02:02
β—‹ 2026-06-04 19:41:26
β—‹NSsk.s5.ans1.ns109.ztomy.com2017-02-11 β†’ 2017-02-11 Β· 4 obs
β—‹ 2016-06-19 23:37:54
● 2017-02-11 17:26:54
β—‹ 2018-10-13 01:40:42
β—‹ 2026-06-04 19:41:26
β—‹NSsk.s5.ans2.ns109.ztomy.com2017-02-11 β†’ 2017-02-11 Β· 4 obs
β—‹ 2016-06-19 23:37:54
● 2017-02-11 17:26:54
β—‹ 2018-10-13 01:40:42
β—‹ 2026-06-04 19:41:26
β—‹MXbitfirewall.com2015-05-19 β†’ 2016-06-19 Β· 4 obs
● 2015-05-19 22:58:52
● 2016-06-19 23:37:54
β—‹ 2017-02-11 17:26:54
β—‹ 2026-06-04 19:41:26
β—‹MXmx.bitfirewall.com2018-10-13 β†’ 2018-10-13 Β· 4 obs
β—‹ 2017-02-11 17:26:54
● 2018-10-13 01:40:42
β—‹ 2026-03-14 01:02:02
β—‹ 2026-06-04 19:41:26
●A13.248.169.482026-03-14 β†’ 2026-06-04 Β· 3 obs
β—‹ 2018-10-13 01:40:42
● 2026-03-14 01:02:02
● 2026-06-04 19:41:26
β—‹A162.144.147.902015-05-19 β†’ 2015-05-19 Β· 3 obs
● 2015-05-19 22:58:52
β—‹ 2015-10-23 19:53:56
β—‹ 2026-06-04 19:41:26
β—‹A198.1.101.2222015-10-23 β†’ 2016-06-19 Β· 5 obs
β—‹ 2015-05-19 22:58:52
● 2015-10-23 19:53:56
● 2016-06-19 23:37:54
β—‹ 2017-02-11 17:26:54
β—‹ 2026-06-04 19:41:26
β—‹A208.91.197.662017-02-11 β†’ 2017-02-11 Β· 4 obs
β—‹ 2016-06-19 23:37:54
● 2017-02-11 17:26:54
β—‹ 2018-10-13 01:40:42
β—‹ 2026-06-04 19:41:26
β—‹A2a05:d014:9da:8c10:306e:3e07:a16f:a5522018-10-13 β†’ 2018-10-13 Β· 4 obs
β—‹ 2017-02-11 17:26:54
● 2018-10-13 01:40:42
β—‹ 2026-03-14 01:02:02
β—‹ 2026-06-04 19:41:26
β—‹A52.58.78.162018-10-13 β†’ 2018-10-13 Β· 4 obs
β—‹ 2017-02-11 17:26:54
● 2018-10-13 01:40:42
β—‹ 2026-03-14 01:02:02
β—‹ 2026-06-04 19:41:26
●A76.223.54.1462026-03-14 β†’ 2026-06-04 Β· 3 obs
β—‹ 2018-10-13 01:40:42
● 2026-03-14 01:02:02
● 2026-06-04 19:41:26
β—‹PTRsk.s5.ans1.ns109.ztomy.com2017-02-11 β†’ 2017-02-11 Β· 3 obs
● 2017-02-11 17:26:54
β—‹ 2026-03-14 01:02:02
β—‹ 2026-06-04 19:41:26

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, i.gtld-servers.net, g.gtld-servers.net, k.gtld-servers.net...-
bitfirewall.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 bitfirewall.com (unsigned zone)

⏱️ Timing

Total: 223ms | 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

The domain bitfirewall.com is parent to mx.bitfirewall.com, ns1.bitfirewall.com and ns2.bitfirewall.com.

IP Addresses

bitfirewall.com points to two IP numbers: 13.248.169.48 and 76.223.54.146.

no.emal.net, demo.commerce5.com, dhaka.co and two other host names share IP numbers with bitfirewall.com.

Name Servers

bitfirewall.com uses two name servers for its delegation: ns1.afternic.com and ns2.afternic.com.

bitfirewall.com uses the same name servers as several other domains β€” among them jusolutions.com, libertarian.co, hostingremix.com and two more.

At least some of bitfirewall.com's name servers are shared with other domains, for example 32655.com, bgsi.org, omgprinting.com and two more.

These name servers tend to be deployed in combination with the name servers verification-iryqusbri9xlks4ssi7d4w.ns101.verify.hn and verification-d3jclucsp89ganyqbydeny.ns101.verify.hn.

The two host names ns1.afternic.com and ns2.afternic.com each have a pair of IP addresses: ns1.afternic.com has 97.74.98.69 and 2603:5:2126::45, and ns2.afternic.com has 173.201.66.69 and 2603:5:2226::45.