fasystems.com - dns.ninja
fasystems.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 | 460df84a-abf4-41d7-bbfc-775594849bd6 | ||||||
| SOA | launch1.spaceship.netsupport@spaceship.com serial=1779962605 | ||||||
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=1784004912 | ||||||
Same first word
fasystems.com |
fasystems.com.sg |
Similar names
afsystems.com.br |
afsystems.it |
afsystems.pl |
afsystems.co.uk |
smssafety.net |
afsystems.com.au |
safetymss.com |
afsystems.com |
safetysms.com |
systemsaf.com |
fsasystem.com |
safsystem.com |
DNS History
15 records (4 active, 11 former)
○NSbuy.internettraffic.com2015-06-14 → 2016-05-09 · 4 obs
● 2015-06-14 07:35:20
● 2016-05-09 01:53:20
○ 2017-01-13 21:01:00
○ 2026-07-14 05:25:18
● 2016-05-09 01:53:20
○ 2017-01-13 21:01:00
○ 2026-07-14 05:25:18
●NSlaunch1.spaceship.net2026-05-01 → 2026-07-14 · 3 obs
○ 2019-02-11 07:54:18
● 2026-05-01 22:51:42
● 2026-07-14 05:25:18
● 2026-05-01 22:51:42
● 2026-07-14 05:25:18
●NSlaunch2.spaceship.net2026-05-01 → 2026-07-14 · 3 obs
○ 2019-02-11 07:54:18
● 2026-05-01 22:51:42
● 2026-07-14 05:25:18
● 2026-05-01 22:51:42
● 2026-07-14 05:25:18
○NSns1.afternic.com2026-05-01 → 2026-07-14 · 2 obs
○ 2026-05-01 22:51:42
○ 2026-07-14 05:25:18
○ 2026-07-14 05:25:18
○NSns1.uniregistrymarket.link2017-01-13 → 2019-02-11 · 5 obs
○ 2016-05-09 01:53:20
● 2017-01-13 21:01:00
● 2019-02-11 07:54:18
○ 2026-05-01 22:51:42
○ 2026-07-14 05:25:18
● 2017-01-13 21:01:00
● 2019-02-11 07:54:18
○ 2026-05-01 22:51:42
○ 2026-07-14 05:25:18
○NSns2.afternic.com2026-05-01 → 2026-07-14 · 2 obs
○ 2026-05-01 22:51:42
○ 2026-07-14 05:25:18
○ 2026-07-14 05:25:18
○NSns2.uniregistrymarket.link2017-01-13 → 2019-02-11 · 5 obs
○ 2016-05-09 01:53:20
● 2017-01-13 21:01:00
● 2019-02-11 07:54:18
○ 2026-05-01 22:51:42
○ 2026-07-14 05:25:18
● 2017-01-13 21:01:00
● 2019-02-11 07:54:18
○ 2026-05-01 22:51:42
○ 2026-07-14 05:25:18
○NSsell.internettraffic.com2015-06-14 → 2016-05-09 · 4 obs
● 2015-06-14 07:35:20
● 2016-05-09 01:53:20
○ 2017-01-13 21:01:00
○ 2026-07-14 05:25:18
● 2016-05-09 01:53:20
○ 2017-01-13 21:01:00
○ 2026-07-14 05:25:18
○MX.2026-05-01 → 2026-07-14 · 2 obs
○ 2026-05-01 22:51:42
○ 2026-07-14 05:25:18
○ 2026-07-14 05:25:18
○A13.248.169.482026-05-01 → 2026-07-14 · 2 obs
○ 2026-05-01 22:51:42
○ 2026-07-14 05:25:18
○ 2026-07-14 05:25:18
●A44.232.173.2492026-05-01 → 2026-07-14 · 3 obs
○ 2019-02-11 07:54:18
● 2026-05-01 22:51:42
● 2026-07-14 05:25:18
● 2026-05-01 22:51:42
● 2026-07-14 05:25:18
●A52.40.42.1132026-05-01 → 2026-07-14 · 3 obs
○ 2019-02-11 07:54:18
● 2026-05-01 22:51:42
● 2026-07-14 05:25:18
● 2026-05-01 22:51:42
● 2026-07-14 05:25:18
○A69.172.201.1532016-05-09 → 2019-02-11 · 5 obs
○ 2016-01-26 12:51:32
● 2016-05-09 01:53:20
● 2019-02-11 07:54:18
○ 2026-05-01 22:51:42
○ 2026-07-14 05:25:18
● 2016-05-09 01:53:20
● 2019-02-11 07:54:18
○ 2026-05-01 22:51:42
○ 2026-07-14 05:25:18
○A69.172.201.2082015-06-14 → 2016-01-26 · 4 obs
● 2015-06-14 07:35:20
● 2016-01-26 12:51:32
○ 2016-05-09 01:53:20
○ 2026-07-14 05:25:18
● 2016-01-26 12:51:32
○ 2016-05-09 01:53:20
○ 2026-07-14 05:25:18
○A76.223.54.1462026-05-01 → 2026-07-14 · 2 obs
○ 2026-05-01 22:51:42
○ 2026-07-14 05:25:18
○ 2026-07-14 05:25:18
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| fasystems.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 fasystems.com (unsigned zone)
⏱️ Timing
Total: 225ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 52.40.42.113, 44.232.173.249 |
| NS | 2 | launch2.spaceship.net, launch1.spaceship.net |
| TXT | 1 | 460df84a-abf4-41d7-bbfc-775594849bd6 |
| SOA | 1 | launch1.spaceship.net support.spaceship. |
Analysis
IP Addresses
fasystems.com has two IP addresses: 44.232.173.249 and 52.40.42.113
relitel.com, vmwareai.com, godofdreams.com and two other host names share IP numbers with fasystems.com.
Name Servers
fasystems.com is delegated to two name servers: launch1.spaceship.net and launch2.spaceship.net.
fasystems.com uses the same name servers as several other domains — among them tonew.com, viruderm.com, hoox.org and two more.
launch1.spaceship.net and launch2.spaceship.net each resolve to two IP addresses: launch1.spaceship.net points to 162.159.26.38 and 2400:cb00:2049:1::a29f:1a26, while launch2.spaceship.net points to 162.159.27.32 and 2400:cb00:2049:1::a29f:1b20.