sftbc.com - dns.ninja
sftbc.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 44.232.173.249🇺🇸 Amazon44.224.0.0/11 EC2 PDX prefix | ||||||
| PTR | ec2-44-232-173-249.us-west-2.compute.amazonaws.com | ||||||
| A | 52.40.42.113🇺🇸 Amazon52.40.0.0/14 EC2 PDX prefix | ||||||
| NS | launch1.spaceship.net ⭐ | ||||||
| A | 2400:cb00:2049:1::a29f:1a26🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.26.38Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | launch2.spaceship.net | ||||||
| A | 2400:cb00:2049:1::a29f:1b20🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.27.32Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| TXT | c2b8f060-3e7c-4dff-9bd6-f465a8edbb59 | ||||||
| SOA | launch1.spaceship.netsupport@spaceship.com serial=1779370261 | ||||||
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.netnstld@verisign-grs.com serial=1783208931 | ||||||
Same first word
sftbc.com |
Similar names
DNS History
29 records (4 active, 25 former)
●NSlaunch1.spaceship.net2026-07-05 → 2026-07-05 · 2 obs
● 2026-07-05 00:00:42
●NSlaunch2.spaceship.net2026-07-05 → 2026-07-05 · 2 obs
● 2026-07-05 00:00:42
○NSns1.afternic.com2026-03-17 → 2026-05-09 · 4 obs
● 2026-03-17 02:43:22
● 2026-05-09 14:07:18
○ 2026-07-05 00:00:42
○NSns1.namebrightdns.com2015-06-05 → 2017-03-18 · 6 obs
● 2016-03-08 22:15:04
○ 2016-07-03 00:58:14
● 2017-03-18 15:26:30
○ 2020-02-13 16:07:34
○ 2026-07-05 00:00:42
○NSns2.afternic.com2026-03-17 → 2026-05-09 · 4 obs
● 2026-03-17 02:43:22
● 2026-05-09 14:07:18
○ 2026-07-05 00:00:42
○NSns2.namebrightdns.com2015-06-05 → 2017-03-18 · 6 obs
● 2016-03-08 22:15:04
○ 2016-07-03 00:58:14
● 2017-03-18 15:26:30
○ 2020-02-13 16:07:34
○ 2026-07-05 00:00:42
○NSns23.domaincontrol.com2020-02-13 → 2020-02-13 · 4 obs
● 2020-02-13 16:07:34
○ 2026-03-17 02:43:22
○ 2026-07-05 00:00:42
○NSns24.domaincontrol.com2020-02-13 → 2020-02-13 · 4 obs
● 2020-02-13 16:07:34
○ 2026-03-17 02:43:22
○ 2026-07-05 00:00:42
○NSnsg1.namebrightdns.com2016-07-03 → 2016-07-03 · 4 obs
● 2016-07-03 00:58:14
○ 2017-03-18 15:26:30
○ 2026-07-05 00:00:42
○NSnsg2.namebrightdns.com2016-07-03 → 2016-07-03 · 4 obs
● 2016-07-03 00:58:14
○ 2017-03-18 15:26:30
○ 2026-07-05 00:00:42
○NSverification-p86drbinxz98mzlv7cb9k6.ns101.verify.hn2026-03-17 → 2026-05-09 · 4 obs
● 2026-03-17 02:43:22
● 2026-05-09 14:07:18
○ 2026-07-05 00:00:42
○MXanmail.namebrightmail.com2015-06-05 → 2015-06-05 · 3 obs
○ 2015-11-05 10:43:50
○ 2026-07-05 00:00:42
○A107.23.198.2402016-07-03 → 2016-07-03 · 4 obs
● 2016-07-03 00:58:14
○ 2017-03-18 15:26:30
○ 2026-07-05 00:00:42
○A13.248.169.482026-03-17 → 2026-05-09 · 4 obs
● 2026-03-17 02:43:22
● 2026-05-09 14:07:18
○ 2026-07-05 00:00:42
○A184.168.221.592020-02-13 → 2020-02-13 · 4 obs
● 2020-02-13 16:07:34
○ 2026-03-17 02:43:22
○ 2026-07-05 00:00:42
○A34.206.157.642017-03-18 → 2017-03-18 · 4 obs
● 2017-03-18 15:26:30
○ 2020-02-13 16:07:34
○ 2026-07-05 00:00:42
●A44.232.173.2492026-07-05 → 2026-07-05 · 2 obs
● 2026-07-05 00:00:42
○A52.0.96.242016-03-08 → 2016-03-08 · 4 obs
● 2016-03-08 22:15:04
○ 2016-07-03 00:58:14
○ 2026-07-05 00:00:42
○A52.4.72.1372016-07-03 → 2016-07-03 · 4 obs
● 2016-07-03 00:58:14
○ 2017-03-18 15:26:30
○ 2026-07-05 00:00:42
●A52.40.42.1132026-07-05 → 2026-07-05 · 2 obs
● 2026-07-05 00:00:42
○A52.71.117.992016-03-08 → 2016-03-08 · 4 obs
● 2016-03-08 22:15:04
○ 2016-07-03 00:58:14
○ 2026-07-05 00:00:42
○A54.174.31.2542015-11-05 → 2015-11-05 · 4 obs
● 2015-11-05 10:43:50
○ 2016-03-08 22:15:04
○ 2026-07-05 00:00:42
○A54.208.74.2152015-11-05 → 2015-11-05 · 4 obs
● 2015-11-05 10:43:50
○ 2016-03-08 22:15:04
○ 2026-07-05 00:00:42
○A54.236.195.152017-03-18 → 2017-03-18 · 4 obs
● 2017-03-18 15:26:30
○ 2020-02-13 16:07:34
○ 2026-07-05 00:00:42
○A54.85.144.1972015-06-05 → 2015-06-05 · 3 obs
○ 2026-03-17 02:43:22
○ 2026-07-05 00:00:42
○A54.85.146.1862015-06-05 → 2015-06-05 · 3 obs
○ 2026-03-17 02:43:22
○ 2026-07-05 00:00:42
○A76.223.54.1462026-03-17 → 2026-05-09 · 4 obs
● 2026-03-17 02:43:22
● 2026-05-09 14:07:18
○ 2026-07-05 00:00:42
○CNAMEhdredirect-lb-399551664.us-east-1.elb.amazonaws.com2015-06-05 → 2016-07-03 · 4 obs
● 2016-07-03 00:58:14
○ 2017-03-18 15:26:30
○ 2026-07-05 00:00:42
○CNAMEhdredirect-lb3-890977680.us-east-1.elb.amazonaws.com2017-03-18 → 2017-03-18 · 4 obs
● 2017-03-18 15:26:30
○ 2020-02-13 16:07:34
○ 2026-07-05 00:00:42
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| sftbc.com | launch2.spaceship.net, launch1.spaceship.net | - |
✅ Authoritative Response
Server:162.159.26.38
NS records: launch2.spaceship.net, launch1.spaceship.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for sftbc.com (unsigned zone)
⏱️ Timing
Total: 659ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 44.232.173.249, 52.40.42.113 |
| NS | 2 | launch1.spaceship.net, launch2.spaceship.net |
| TXT | 1 | c2b8f060-3e7c-4dff-9bd6-f465a8edbb59 |
| SOA | 1 | launch1.spaceship.net support.spaceship. |
Analysis
IP Addresses
sftbc.com has two IP addresses: 44.232.173.249 and 52.40.42.113
Additional host names — ssuda.com, protocol.ca, logolita.com and two others — share IP numbers with sftbc.com.
Name Servers
The NS records for sftbc.com delegate to launch1.spaceship.net and launch2.spaceship.net.
sftbc.com shares its name server setup with other domains, including blog66real.shop, credited.in, ggcity.com and two others.
sftbc.com and other domains like kdvhesapla.com share at least a portion of their name servers.
launch1.spaceship.net resolves to 162.159.26.38 and 2400:cb00:2049:1::a29f:1a26. Likewise, launch2.spaceship.net resolves to 162.159.27.32 and 2400:cb00:2049:1::a29f:1b20 — two IP addresses apiece.