remote-working.com - dns.ninja
remote-working.com
| DNSSEC | π Signed (DS record present) | ||||||
| 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 | ||||||
| SOA | launch1.spaceship.netsupport@spaceship.com serial=1784569265 | ||||||
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=1785492082 | ||||||
Previously MX for
remote-working.com |
Same first word
remote-working.com |
remote-working.net |
DNS History
24 records (4 active, 20 former)
βNSlaunch1.spaceship.net2026-03-24 β 2026-07-31 Β· 3 obs
β 2026-03-24 17:00:58
β 2026-07-31 10:14:04
βNSlaunch2.spaceship.net2026-03-24 β 2026-07-31 Β· 3 obs
β 2026-03-24 17:00:58
β 2026-07-31 10:14:04
βNSns1.afternic.com2026-03-24 β 2026-07-31 Β· 2 obs
β 2026-07-31 10:14:04
βNSns1.namebrightdns.com2017-03-23 β 2017-03-23 Β· 4 obs
β 2017-03-23 10:57:36
β 2020-02-04 01:10:06
β 2026-07-31 10:14:04
βNSns1.xserver.jp2015-07-22 β 2016-07-14 Β· 4 obs
β 2016-07-14 05:32:38
β 2017-03-23 10:57:36
β 2026-07-31 10:14:04
βNSns2.afternic.com2026-03-24 β 2026-07-31 Β· 2 obs
β 2026-07-31 10:14:04
βNSns2.namebrightdns.com2017-03-23 β 2017-03-23 Β· 4 obs
β 2017-03-23 10:57:36
β 2020-02-04 01:10:06
β 2026-07-31 10:14:04
βNSns2.xserver.jp2015-07-22 β 2016-07-14 Β· 4 obs
β 2016-07-14 05:32:38
β 2017-03-23 10:57:36
β 2026-07-31 10:14:04
βNSns3.xserver.jp2015-07-22 β 2016-07-14 Β· 4 obs
β 2016-07-14 05:32:38
β 2017-03-23 10:57:36
β 2026-07-31 10:14:04
βNSns4.xserver.jp2015-07-22 β 2016-07-14 Β· 4 obs
β 2016-07-14 05:32:38
β 2017-03-23 10:57:36
β 2026-07-31 10:14:04
βNSns5.xserver.jp2015-07-22 β 2016-07-14 Β· 4 obs
β 2016-07-14 05:32:38
β 2017-03-23 10:57:36
β 2026-07-31 10:14:04
βNSnsg1.namebrightdns.com2020-02-04 β 2020-02-04 Β· 4 obs
β 2020-02-04 01:10:06
β 2026-03-24 17:00:58
β 2026-07-31 10:14:04
βNSnsg2.namebrightdns.com2020-02-04 β 2020-02-04 Β· 4 obs
β 2020-02-04 01:10:06
β 2026-03-24 17:00:58
β 2026-07-31 10:14:04
βMX.2026-03-24 β 2026-07-31 Β· 2 obs
β 2026-07-31 10:14:04
βMXremote-working.com2015-07-22 β 2016-07-14 Β· 4 obs
β 2016-07-14 05:32:38
β 2017-03-23 10:57:36
β 2026-07-31 10:14:04
βA120.136.10.772015-07-22 β 2016-07-14 Β· 4 obs
β 2016-07-14 05:32:38
β 2017-03-23 10:57:36
β 2026-07-31 10:14:04
βA13.248.169.482026-03-24 β 2026-07-31 Β· 2 obs
β 2026-07-31 10:14:04
βA34.206.157.642017-03-23 β 2017-03-23 Β· 4 obs
β 2017-03-23 10:57:36
β 2020-02-04 01:10:06
β 2026-07-31 10:14:04
βA44.232.173.2492026-03-24 β 2026-07-31 Β· 3 obs
β 2026-03-24 17:00:58
β 2026-07-31 10:14:04
βA52.40.42.1132026-03-24 β 2026-07-31 Β· 3 obs
β 2026-03-24 17:00:58
β 2026-07-31 10:14:04
βA54.236.195.152017-03-23 β 2017-03-23 Β· 4 obs
β 2017-03-23 10:57:36
β 2020-02-04 01:10:06
β 2026-07-31 10:14:04
βA76.223.54.1462026-03-24 β 2026-07-31 Β· 2 obs
β 2026-07-31 10:14:04
βCNAMEhdredirect-lb3-890977680.us-east-1.elb.amazonaws.com2017-03-23 β 2017-03-23 Β· 3 obs
β 2020-02-04 01:10:06
β 2026-07-31 10:14:04
βCNAMEhdredirect-lb5-1afb6e2973825a56.elb.us-east-1.amazonaws.com2020-02-04 β 2020-02-04 Β· 4 obs
β 2020-02-04 01:10:06
β 2026-03-24 17:00:58
β 2026-07-31 10:14:04
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | i.gtld-servers.net, b.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net... | - |
| remote-working.com | launch2.spaceship.net, launch1.spaceship.net | - |
β Authoritative Response
Server:162.159.26.38
NS records: launch2.spaceship.net, launch1.spaceship.net
π DNSSEC Status
π Secure (DNSSEC validated)
Chain of trust verified from root to domain
β±οΈ Timing
Total: 407ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 44.232.173.249, 52.40.42.113 |
| NS | 2 | launch2.spaceship.net, launch1.spaceship.net |
| SOA | 1 | launch1.spaceship.net support.spaceship. |
Analysis
IP Addresses
remote-working.com points to the IP addresses 44.232.173.249 and 52.40.42.113
Among the host names that share IP numbers with remote-working.com are prominent.gg, terrains.de, connecty.io and two others.
Name Servers
remote-working.com has two authoritative name servers β launch1.spaceship.net and launch2.spaceship.net.
remote-working.com has the same name server delegation as a number of other domains, such as sub4fun.org, nextzone.de, opennfr.com and two more.
At least some of remote-working.com's name servers are shared with other domains, for example yanida.com and bydig.com.
Both launch1.spaceship.net and launch2.spaceship.net have two IP addresses each. launch1.spaceship.net resolves to 162.159.26.38 and 2400:cb00:2049:1::a29f:1a26; launch2.spaceship.net resolves to 162.159.27.32 and 2400:cb00:2049:1::a29f:1b20.