securityintelligencegroup.com - dns.ninja
securityintelligencegroup.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 | 38254d03-0af6-411f-91da-0f94dc5d86fa | ||||||
| SOA | launch1.spaceship.netsupport@spaceship.com serial=1785002802 | ||||||
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=1785005872 | ||||||
Same first word
securityintelligencegroup.com |
DNS History
17 records (4 active, 13 former)
●NSlaunch1.spaceship.net2026-07-25 → 2026-07-25 · 2 obs
○ 2026-05-19 09:49:46
● 2026-07-25 19:14:30
● 2026-07-25 19:14:30
●NSlaunch2.spaceship.net2026-07-25 → 2026-07-25 · 2 obs
○ 2026-05-19 09:49:46
● 2026-07-25 19:14:30
● 2026-07-25 19:14:30
○NSns1.afternic.com2026-05-19 → 2026-05-19 · 3 obs
○ 2017-05-23 03:22:24
● 2026-05-19 09:49:46
○ 2026-07-25 19:14:30
● 2026-05-19 09:49:46
○ 2026-07-25 19:14:30
○NSns1.sedoparking.com2026-05-19 → 2026-05-19 · 3 obs
○ 2017-05-23 03:22:24
● 2026-05-19 09:49:46
○ 2026-07-25 19:14:30
● 2026-05-19 09:49:46
○ 2026-07-25 19:14:30
○NSns2.afternic.com2026-05-19 → 2026-05-19 · 3 obs
○ 2017-05-23 03:22:24
● 2026-05-19 09:49:46
○ 2026-07-25 19:14:30
● 2026-05-19 09:49:46
○ 2026-07-25 19:14:30
○NSns2.sedoparking.com2026-05-19 → 2026-05-19 · 3 obs
○ 2017-05-23 03:22:24
● 2026-05-19 09:49:46
○ 2026-07-25 19:14:30
● 2026-05-19 09:49:46
○ 2026-07-25 19:14:30
○NSns35.domaincontrol.com2015-05-14 → 2017-05-23 · 4 obs
● 2015-05-14 16:45:24
● 2017-05-23 03:22:24
○ 2026-05-19 09:49:46
○ 2026-07-25 19:14:30
● 2017-05-23 03:22:24
○ 2026-05-19 09:49:46
○ 2026-07-25 19:14:30
○NSns36.domaincontrol.com2015-05-14 → 2017-05-23 · 4 obs
● 2015-05-14 16:45:24
● 2017-05-23 03:22:24
○ 2026-05-19 09:49:46
○ 2026-07-25 19:14:30
● 2017-05-23 03:22:24
○ 2026-05-19 09:49:46
○ 2026-07-25 19:14:30
○MXlocalhost2026-05-19 → 2026-07-19 · 5 obs
○ 2017-05-23 03:22:24
● 2026-05-19 09:49:46
○ 2026-06-04 04:17:48
● 2026-07-19 01:33:36
○ 2026-07-25 19:14:30
● 2026-05-19 09:49:46
○ 2026-06-04 04:17:48
● 2026-07-19 01:33:36
○ 2026-07-25 19:14:30
○MXmailstore1.secureserver.net2015-05-14 → 2017-05-23 · 4 obs
● 2015-05-14 16:45:24
● 2017-05-23 03:22:24
○ 2026-05-19 09:49:46
○ 2026-07-25 19:14:30
● 2017-05-23 03:22:24
○ 2026-05-19 09:49:46
○ 2026-07-25 19:14:30
○MXsmtp.secureserver.net2015-05-14 → 2017-05-23 · 4 obs
● 2015-05-14 16:45:24
● 2017-05-23 03:22:24
○ 2026-05-19 09:49:46
○ 2026-07-25 19:14:30
● 2017-05-23 03:22:24
○ 2026-05-19 09:49:46
○ 2026-07-25 19:14:30
○A13.248.169.482026-05-19 → 2026-07-23 · 5 obs
○ 2017-05-23 03:22:24
● 2026-05-19 09:49:46
○ 2026-07-10 04:34:32
● 2026-07-23 11:07:24
○ 2026-07-25 19:14:30
● 2026-05-19 09:49:46
○ 2026-07-10 04:34:32
● 2026-07-23 11:07:24
○ 2026-07-25 19:14:30
○A184.168.221.62015-05-14 → 2017-05-23 · 4 obs
● 2015-05-14 16:45:24
● 2017-05-23 03:22:24
○ 2026-05-19 09:49:46
○ 2026-07-25 19:14:30
● 2017-05-23 03:22:24
○ 2026-05-19 09:49:46
○ 2026-07-25 19:14:30
●A44.232.173.2492026-07-25 → 2026-07-25 · 2 obs
○ 2026-07-23 11:07:24
● 2026-07-25 19:14:30
● 2026-07-25 19:14:30
●A52.40.42.1132026-07-25 → 2026-07-25 · 2 obs
○ 2026-07-23 11:07:24
● 2026-07-25 19:14:30
● 2026-07-25 19:14:30
○A64.190.63.2222026-07-10 → 2026-07-10 · 4 obs
○ 2026-05-19 09:49:46
● 2026-07-10 04:34:32
○ 2026-07-23 11:07:24
○ 2026-07-25 19:14:30
● 2026-07-10 04:34:32
○ 2026-07-23 11:07:24
○ 2026-07-25 19:14:30
○A76.223.54.1462026-05-19 → 2026-07-23 · 5 obs
○ 2017-05-23 03:22:24
● 2026-05-19 09:49:46
○ 2026-07-10 04:34:32
● 2026-07-23 11:07:24
○ 2026-07-25 19:14:30
● 2026-05-19 09:49:46
○ 2026-07-10 04:34:32
● 2026-07-23 11:07:24
○ 2026-07-25 19:14:30
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | g.gtld-servers.net, l.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net... | - |
| securityintelligencegroup.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 securityintelligencegroup.com (unsigned zone)
⏱️ Timing
Total: 441ms | 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 | 38254d03-0af6-411f-91da-0f94dc5d86fa |
| SOA | 1 | launch1.spaceship.net support.spaceship. |
Analysis
IP Addresses
securityintelligencegroup.com directs to two IP numbers, 44.232.173.249 and 52.40.42.113
claudetag.cc, letup.com, strict.co plus two other host names have IP numbers in common with securityintelligencegroup.com.
Name Servers
DNS delegation for securityintelligencegroup.com points to two name servers: launch1.spaceship.net and launch2.spaceship.net.
The name server configuration of securityintelligencegroup.com is shared with other domains, for instance harperpets.com, nichiro.com, jogs.ca and two others.
launch1.spaceship.net directs to 162.159.26.38 and 2400:cb00:2049:1::a29f:1a26. launch2.spaceship.net directs to 162.159.27.32 and 2400:cb00:2049:1::a29f:1b20. Each host name carries two IP addresses.