bitcom.co - dns.ninja
bitcom.co
| DNSSEC | ⚠️ Not signed | ||||||
| A | 13.248.169.48🇺🇸 Amazon13.248.160.0/20 | ||||||
| PTR | a904c694c05102f30.awsglobalaccelerator.com | ||||||
| A | 76.223.54.146🇺🇸 Amazon76.223.48.0/20 | ||||||
| NS | ns2.afternic.com ⭐ | ||||||
| A | 2603:5:2226::45🇺🇸 GODADDY-DNS2603:5:2220::/44 | ||||||
| PTR | ns2.afternic.com | ||||||
| A | 173.201.66.69🇺🇸 GODADDY-DNS173.201.66.0/23 | ||||||
| PTR | ns2.afternic.com | ||||||
| NS | ns1.afternic.com | ||||||
| A | 2603:5:2126::45🇺🇸 GODADDY-DNS2603:5:2120::/44 | ||||||
| PTR | ns1.afternic.com | ||||||
| A | 97.74.98.69🇺🇸 GODADDY-DNS97.74.98.0/23 | ||||||
| PTR | ns1.afternic.com | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | ns2.afternic.comdns@jomax.net serial=1 | ||||||
co
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns0.centralnic.net ⭐ | ||||||
| NS | a.registrydns.co | ||||||
| NS | b.registrydns.co | ||||||
| NS | c.registrydns.co | ||||||
| NS | d.registrydns.co | ||||||
| SOA | ns0.centralnic.nethostmaster@centralnic.net serial=1759705276 | ||||||
Previously MX for
bitcom.co |
Subdomains
mx.bitcom.co |
Same first word
Similar names
DNS History
24 records (4 active, 20 former)
●NSns1.afternic.com2026-04-03 → 2026-07-14 · 3 obs
● 2026-04-03 06:59:18
● 2026-07-14 09:14:22
○NSns1.eftydns.com2016-10-16 → 2016-10-16 · 4 obs
● 2016-10-16 17:27:52
○ 2017-01-05 02:27:40
○ 2026-07-14 09:14:22
○NSns1.linux4.aryanic.org2015-08-04 → 2015-11-25 · 4 obs
● 2015-11-25 13:32:04
○ 2016-03-11 13:57:26
○ 2026-07-14 09:14:22
○NSns1.undeveloped.com2017-01-05 → 2017-01-05 · 4 obs
● 2017-01-05 02:27:40
○ 2017-07-12 20:20:40
○ 2026-07-14 09:14:22
○NSns1.uniregistrymarket.link2017-07-12 → 2017-08-24 · 5 obs
● 2017-07-12 20:20:40
● 2017-08-24 01:10:26
○ 2026-04-03 06:59:18
○ 2026-07-14 09:14:22
●NSns2.afternic.com2026-04-03 → 2026-07-14 · 3 obs
● 2026-04-03 06:59:18
● 2026-07-14 09:14:22
○NSns2.eftydns.com2016-10-16 → 2016-10-16 · 4 obs
● 2016-10-16 17:27:52
○ 2017-01-05 02:27:40
○ 2026-07-14 09:14:22
○NSns2.linux4.aryanic.org2015-08-04 → 2015-11-25 · 4 obs
● 2015-11-25 13:32:04
○ 2016-03-11 13:57:26
○ 2026-07-14 09:14:22
○NSns2.undeveloped.com2017-01-05 → 2017-01-05 · 4 obs
● 2017-01-05 02:27:40
○ 2017-07-12 20:20:40
○ 2026-07-14 09:14:22
○NSns2.uniregistrymarket.link2017-07-12 → 2017-08-24 · 5 obs
● 2017-07-12 20:20:40
● 2017-08-24 01:10:26
○ 2026-04-03 06:59:18
○ 2026-07-14 09:14:22
○MX.2026-04-03 → 2026-07-14 · 2 obs
○ 2026-07-14 09:14:22
○MXbitcom.co2015-08-04 → 2015-11-25 · 4 obs
● 2015-11-25 13:32:04
○ 2016-03-11 13:57:26
○ 2026-07-14 09:14:22
○MXmail.efty.com2016-10-16 → 2016-10-16 · 4 obs
● 2016-10-16 17:27:52
○ 2017-01-05 02:27:40
○ 2026-07-14 09:14:22
○MXmx.bitcom.co2017-01-05 → 2017-01-05 · 4 obs
● 2017-01-05 02:27:40
○ 2017-07-12 20:20:40
○ 2026-07-14 09:14:22
○A119.81.170.182016-10-16 → 2016-10-16 · 4 obs
● 2016-10-16 17:27:52
○ 2017-01-05 02:27:40
○ 2026-07-14 09:14:22
●A13.248.169.482026-04-03 → 2026-07-14 · 3 obs
● 2026-04-03 06:59:18
● 2026-07-14 09:14:22
○A52.4.36.1862016-03-11 → 2016-03-11 · 4 obs
● 2016-03-11 13:57:26
○ 2016-10-16 17:27:52
○ 2026-07-14 09:14:22
○A52.58.78.162017-01-05 → 2017-01-05 · 4 obs
● 2017-01-05 02:27:40
○ 2017-07-12 20:20:40
○ 2026-07-14 09:14:22
○A52.6.33.362016-03-11 → 2016-03-11 · 4 obs
● 2016-03-11 13:57:26
○ 2016-10-16 17:27:52
○ 2026-07-14 09:14:22
○A69.172.201.1532017-07-12 → 2017-08-24 · 5 obs
● 2017-07-12 20:20:40
● 2017-08-24 01:10:26
○ 2026-04-03 06:59:18
○ 2026-07-14 09:14:22
●A76.223.54.1462026-04-03 → 2026-07-14 · 3 obs
● 2026-04-03 06:59:18
● 2026-07-14 09:14:22
○A85.17.205.2122015-08-04 → 2015-11-25 · 4 obs
● 2015-11-25 13:32:04
○ 2016-03-11 13:57:26
○ 2026-07-14 09:14:22
○CNAMEpr-co-suspensions.neuweb.biz2016-03-11 → 2016-03-11 · 3 obs
○ 2016-10-16 17:27:52
○ 2026-07-14 09:14:22
○CNAMEws-pr-web-suspensionpages-1962938698.us-east-1.elb.amazonaws.com2016-03-11 → 2016-03-11 · 3 obs
○ 2016-10-16 17:27:52
○ 2026-07-14 09:14:22
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| co | c.registrydns.co, b.registrydns.co, d.registrydns.co, a.registrydns.co | - |
| bitcom.co | ns1.afternic.com, ns2.afternic.com | - |
✅ Authoritative Response
Server:97.74.98.69
NS records: ns1.afternic.com, ns2.afternic.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for bitcom.co (unsigned zone)
⏱️ Timing
Total: 139ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 76.223.54.146, 13.248.169.48 |
| NS | 2 | ns1.afternic.com, ns2.afternic.com |
| MX | 1 | . (pri: 0) |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | ns1.afternic.com dns.jomax.net |
Analysis
Hierarchy
bitcom.co is a parent domain of mx.bitcom.co.
IP Addresses
bitcom.co resolves to the IP addresses 13.248.169.48 and 76.223.54.146
Additional host names — qzwn.com, marriagesaved.publicsets.com, dexmotors.com and two others — share IP numbers with bitcom.co.
Name Servers
bitcom.co has two authoritative name servers — ns1.afternic.com and ns2.afternic.com.
bitcom.co shares its name server setup with other domains, including mikutel.com, fieldtrain.com, uuid.us and two others.
bitcom.co shares at least some of its name servers with other domains, including elitegamers.co, diefstalbescherming.com, www.taoyuanyou.com and two others.
These name servers are frequently seen alongside the name servers verification-vesbet7nkettdw2mc9cgox.ns101.verify.hn, verification-m3erh32ujyoastvophjvuz.ns101.verify.hn, verification-imdej9cdcjwbr9fxdufjlq.ns101.verify.hn and verification-hz5ut8vgny9r5wonmcftfz.ns101.verify.hn.
Both ns1.afternic.com and ns2.afternic.com have two IP addresses each. ns1.afternic.com resolves to 97.74.98.69 and 2603:5:2126::45; ns2.afternic.com resolves to 173.201.66.69 and 2603:5:2226::45.