managermax.com - dns.ninja
managermax.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 | 07cad280-3d76-4377-9813-be0852ffe6e4 | ||||||
| SOA | launch1.spaceship.netsupport@spaceship.com serial=1784955698 | ||||||
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=1785363957 | ||||||
Same first word
managermax.com |
Similar names
maxmanager.info |
maxmanager.de |
maxmanager.com |
gammarenax.com |
gammarenax.ch |
maxmanager.xyz |
maxmanager.com.br |
DNS History
13 records (4 active, 9 former)
●NSlaunch1.spaceship.net2026-04-07 → 2026-07-29 · 3 obs
○ 2026-02-17 10:34:02
● 2026-04-07 12:21:42
● 2026-07-29 22:44:56
● 2026-04-07 12:21:42
● 2026-07-29 22:44:56
●NSlaunch2.spaceship.net2026-04-07 → 2026-07-29 · 3 obs
○ 2026-02-17 10:34:02
● 2026-04-07 12:21:42
● 2026-07-29 22:44:56
● 2026-04-07 12:21:42
● 2026-07-29 22:44:56
○NSns1.parkingcrew.net2026-02-17 → 2026-02-17 · 4 obs
○ 2017-04-05 09:52:38
● 2026-02-17 10:34:02
○ 2026-04-07 12:21:42
○ 2026-07-29 22:44:56
● 2026-02-17 10:34:02
○ 2026-04-07 12:21:42
○ 2026-07-29 22:44:56
○NSns19.domaincontrol.com2015-06-10 → 2017-04-05 · 4 obs
● 2015-06-10 21:21:28
● 2017-04-05 09:52:38
○ 2026-02-17 10:34:02
○ 2026-07-29 22:44:56
● 2017-04-05 09:52:38
○ 2026-02-17 10:34:02
○ 2026-07-29 22:44:56
○NSns2.parkingcrew.net2026-02-17 → 2026-02-17 · 4 obs
○ 2017-04-05 09:52:38
● 2026-02-17 10:34:02
○ 2026-04-07 12:21:42
○ 2026-07-29 22:44:56
● 2026-02-17 10:34:02
○ 2026-04-07 12:21:42
○ 2026-07-29 22:44:56
○NSns20.domaincontrol.com2017-04-05 → 2017-04-05 · 4 obs
○ 2015-06-10 21:21:28
● 2017-04-05 09:52:38
○ 2026-02-17 10:34:02
○ 2026-07-29 22:44:56
● 2017-04-05 09:52:38
○ 2026-02-17 10:34:02
○ 2026-07-29 22:44:56
○MXmail.h-email.net2026-02-17 → 2026-02-17 · 4 obs
○ 2017-04-05 09:52:38
● 2026-02-17 10:34:02
○ 2026-04-07 12:21:42
○ 2026-07-29 22:44:56
● 2026-02-17 10:34:02
○ 2026-04-07 12:21:42
○ 2026-07-29 22:44:56
○MXmailstore1.secureserver.net2015-06-10 → 2017-04-05 · 4 obs
● 2015-06-10 21:21:28
● 2017-04-05 09:52:38
○ 2026-02-17 10:34:02
○ 2026-07-29 22:44:56
● 2017-04-05 09:52:38
○ 2026-02-17 10:34:02
○ 2026-07-29 22:44:56
○MXsmtp.secureserver.net2015-06-10 → 2017-04-05 · 4 obs
● 2015-06-10 21:21:28
● 2017-04-05 09:52:38
○ 2026-02-17 10:34:02
○ 2026-07-29 22:44:56
● 2017-04-05 09:52:38
○ 2026-02-17 10:34:02
○ 2026-07-29 22:44:56
○A104.247.81.992026-02-17 → 2026-02-17 · 4 obs
○ 2017-04-05 09:52:38
● 2026-02-17 10:34:02
○ 2026-04-07 12:21:42
○ 2026-07-29 22:44:56
● 2026-02-17 10:34:02
○ 2026-04-07 12:21:42
○ 2026-07-29 22:44:56
●A44.232.173.2492026-04-07 → 2026-07-29 · 3 obs
○ 2026-02-17 10:34:02
● 2026-04-07 12:21:42
● 2026-07-29 22:44:56
● 2026-04-07 12:21:42
● 2026-07-29 22:44:56
○A50.63.202.272015-06-10 → 2017-04-05 · 4 obs
● 2015-06-10 21:21:28
● 2017-04-05 09:52:38
○ 2026-02-17 10:34:02
○ 2026-07-29 22:44:56
● 2017-04-05 09:52:38
○ 2026-02-17 10:34:02
○ 2026-07-29 22:44:56
●A52.40.42.1132026-04-07 → 2026-07-29 · 3 obs
○ 2026-02-17 10:34:02
● 2026-04-07 12:21:42
● 2026-07-29 22:44:56
● 2026-04-07 12:21:42
● 2026-07-29 22:44:56
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | b.gtld-servers.net, c.gtld-servers.net, i.gtld-servers.net, k.gtld-servers.net... | - |
| managermax.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 managermax.com (unsigned zone)
⏱️ Timing
Total: 353ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 44.232.173.249, 52.40.42.113 |
| NS | 2 | launch2.spaceship.net, launch1.spaceship.net |
| TXT | 1 | 07cad280-3d76-4377-9813-be0852ffe6e4 |
| SOA | 1 | launch1.spaceship.net support.spaceship. |
Analysis
IP Addresses
managermax.com has two IP addresses: 44.232.173.249 and 52.40.42.113
Two other host names, along with hilook.net, javamac.com and posrose.com, also share IP numbers with managermax.com.
Name Servers
managermax.com is served by two delegated name servers, launch1.spaceship.net and launch2.spaceship.net.
managermax.com shares its NS records with other domains, for example persialove.com, ze.cc, appicon.build and two others.
Each of the two host names carries two IP addresses: launch1.spaceship.net points to 162.159.26.38 and 2400:cb00:2049:1::a29f:1a26, and launch2.spaceship.net points to 162.159.27.32 and 2400:cb00:2049:1::a29f:1b20.