prophp.com - dns.ninja
prophp.com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| A | 15.197.162.184🇺🇸 Amazon15.197.160.0/20 | ||||||
| PTR | a6008b9e03ae11d1d.awsglobalaccelerator.com | ||||||
| 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=1783061758 | ||||||
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=1783273531 | ||||||
Same first word
Similar names
DNS History
25 records (3 active, 22 former)
○NSdns1.name-services.com2015-08-18 → 2016-03-08 · 4 obs
● 2015-08-18 06:25:46
● 2016-03-08 17:00:42
○ 2017-02-11 01:37:18
○ 2026-07-05 17:46:02
● 2016-03-08 17:00:42
○ 2017-02-11 01:37:18
○ 2026-07-05 17:46:02
○NSdns2.name-services.com2015-08-18 → 2016-03-08 · 4 obs
● 2015-08-18 06:25:46
● 2016-03-08 17:00:42
○ 2017-02-11 01:37:18
○ 2026-07-05 17:46:02
● 2016-03-08 17:00:42
○ 2017-02-11 01:37:18
○ 2026-07-05 17:46:02
○NSdns3.name-services.com2015-08-18 → 2016-03-08 · 4 obs
● 2015-08-18 06:25:46
● 2016-03-08 17:00:42
○ 2017-02-11 01:37:18
○ 2026-07-05 17:46:02
● 2016-03-08 17:00:42
○ 2017-02-11 01:37:18
○ 2026-07-05 17:46:02
○NSdns4.name-services.com2015-08-18 → 2016-03-08 · 4 obs
● 2015-08-18 06:25:46
● 2016-03-08 17:00:42
○ 2017-02-11 01:37:18
○ 2026-07-05 17:46:02
● 2016-03-08 17:00:42
○ 2017-02-11 01:37:18
○ 2026-07-05 17:46:02
○NSdns5.name-services.com2015-08-18 → 2016-03-08 · 4 obs
● 2015-08-18 06:25:46
● 2016-03-08 17:00:42
○ 2017-02-11 01:37:18
○ 2026-07-05 17:46:02
● 2016-03-08 17:00:42
○ 2017-02-11 01:37:18
○ 2026-07-05 17:46:02
●NSlaunch1.spaceship.net2026-07-05 → 2026-07-05 · 3 obs
○ 2026-05-09 23:33:38
● 2026-07-05 17:45:58
● 2026-07-05 17:46:02
● 2026-07-05 17:45:58
● 2026-07-05 17:46:02
●NSlaunch2.spaceship.net2026-07-05 → 2026-07-05 · 3 obs
○ 2026-05-09 23:33:38
● 2026-07-05 17:45:58
● 2026-07-05 17:46:02
● 2026-07-05 17:45:58
● 2026-07-05 17:46:02
○NSns.uniregistry.net2017-02-11 → 2017-02-11 · 4 obs
○ 2016-03-08 17:00:42
● 2017-02-11 01:37:18
○ 2018-11-20 14:25:28
○ 2026-07-05 17:46:02
● 2017-02-11 01:37:18
○ 2018-11-20 14:25:28
○ 2026-07-05 17:46:02
○NSns1.atom.com2026-02-23 → 2026-05-09 · 5 obs
○ 2018-11-20 14:25:28
● 2026-02-23 05:08:32
● 2026-05-09 23:33:38
○ 2026-07-05 17:45:58
○ 2026-07-05 17:46:02
● 2026-02-23 05:08:32
● 2026-05-09 23:33:38
○ 2026-07-05 17:45:58
○ 2026-07-05 17:46:02
○NSns1.uniregistry-dns.com2017-02-11 → 2017-02-11 · 4 obs
○ 2016-03-08 17:00:42
● 2017-02-11 01:37:18
○ 2018-11-20 14:25:28
○ 2026-07-05 17:46:02
● 2017-02-11 01:37:18
○ 2018-11-20 14:25:28
○ 2026-07-05 17:46:02
○NSns1.uniregistry-dns.net2017-02-11 → 2017-02-11 · 4 obs
○ 2016-03-08 17:00:42
● 2017-02-11 01:37:18
○ 2018-11-20 14:25:28
○ 2026-07-05 17:46:02
● 2017-02-11 01:37:18
○ 2018-11-20 14:25:28
○ 2026-07-05 17:46:02
○NSns2.atom.com2026-02-23 → 2026-05-09 · 5 obs
○ 2018-11-20 14:25:28
● 2026-02-23 05:08:32
● 2026-05-09 23:33:38
○ 2026-07-05 17:45:58
○ 2026-07-05 17:46:02
● 2026-02-23 05:08:32
● 2026-05-09 23:33:38
○ 2026-07-05 17:45:58
○ 2026-07-05 17:46:02
○NSns2.uniregistry-dns.com2017-02-11 → 2017-02-11 · 4 obs
○ 2016-03-08 17:00:42
● 2017-02-11 01:37:18
○ 2018-11-20 14:25:28
○ 2026-07-05 17:46:02
● 2017-02-11 01:37:18
○ 2018-11-20 14:25:28
○ 2026-07-05 17:46:02
○NSns2.uniregistry-dns.net2017-02-11 → 2017-02-11 · 4 obs
○ 2016-03-08 17:00:42
● 2017-02-11 01:37:18
○ 2018-11-20 14:25:28
○ 2026-07-05 17:46:02
● 2017-02-11 01:37:18
○ 2018-11-20 14:25:28
○ 2026-07-05 17:46:02
○NSns3.epik.com2018-11-20 → 2018-11-20 · 4 obs
○ 2017-02-11 01:37:18
● 2018-11-20 14:25:28
○ 2026-02-23 05:08:32
○ 2026-07-05 17:46:02
● 2018-11-20 14:25:28
○ 2026-02-23 05:08:32
○ 2026-07-05 17:46:02
○NSns4.epik.com2018-11-20 → 2018-11-20 · 4 obs
○ 2017-02-11 01:37:18
● 2018-11-20 14:25:28
○ 2026-02-23 05:08:32
○ 2026-07-05 17:46:02
● 2018-11-20 14:25:28
○ 2026-02-23 05:08:32
○ 2026-07-05 17:46:02
○MXeforwardct.name-services.com2015-08-18 → 2015-08-18 · 3 obs
● 2015-08-18 06:25:46
○ 2015-12-04 04:48:40
○ 2026-07-05 17:46:02
○ 2015-12-04 04:48:40
○ 2026-07-05 17:46:02
○MXeforwardct2.name-services.com2015-08-18 → 2015-08-18 · 3 obs
● 2015-08-18 06:25:46
○ 2015-12-04 04:48:40
○ 2026-07-05 17:46:02
○ 2015-12-04 04:48:40
○ 2026-07-05 17:46:02
○MXeforwardct3.name-services.com2015-08-18 → 2015-08-18 · 3 obs
● 2015-08-18 06:25:46
○ 2015-12-04 04:48:40
○ 2026-07-05 17:46:02
○ 2015-12-04 04:48:40
○ 2026-07-05 17:46:02
●A15.197.162.1842026-07-05 → 2026-07-05 · 3 obs
○ 2026-05-09 23:33:38
● 2026-07-05 17:45:58
● 2026-07-05 17:46:02
● 2026-07-05 17:45:58
● 2026-07-05 17:46:02
○A162.243.47.2142016-07-01 → 2016-07-01 · 4 obs
○ 2016-03-08 17:00:42
● 2016-07-01 03:56:36
○ 2017-02-11 01:37:18
○ 2026-07-05 17:46:02
● 2016-07-01 03:56:36
○ 2017-02-11 01:37:18
○ 2026-07-05 17:46:02
○A52.20.84.622026-02-23 → 2026-05-09 · 5 obs
○ 2017-02-11 01:37:18
● 2026-02-23 05:08:32
● 2026-05-09 23:33:38
○ 2026-07-05 17:45:58
○ 2026-07-05 17:46:02
● 2026-02-23 05:08:32
● 2026-05-09 23:33:38
○ 2026-07-05 17:45:58
○ 2026-07-05 17:46:02
○A98.124.198.12015-08-18 → 2015-08-18 · 3 obs
● 2015-08-18 06:25:46
○ 2015-12-04 04:48:40
○ 2026-07-05 17:46:02
○ 2015-12-04 04:48:40
○ 2026-07-05 17:46:02
○A98.124.199.12015-08-18 → 2015-08-18 · 3 obs
● 2015-08-18 06:25:46
○ 2017-02-11 01:37:18
○ 2026-07-05 17:46:02
○ 2017-02-11 01:37:18
○ 2026-07-05 17:46:02
○A98.124.199.192015-12-04 → 2016-03-08 · 5 obs
○ 2015-08-18 06:25:46
● 2015-12-04 04:48:40
● 2016-03-08 17:00:42
○ 2016-07-01 03:56:36
○ 2026-07-05 17:46:02
● 2015-12-04 04:48:40
● 2016-03-08 17:00:42
○ 2016-07-01 03:56:36
○ 2026-07-05 17:46:02
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| prophp.com | launch2.spaceship.net, launch1.spaceship.net | - |
✅ Authoritative Response
Server:162.159.27.32
NS records: launch2.spaceship.net, launch1.spaceship.net
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 337ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 15.197.162.184 |
| NS | 2 | launch1.spaceship.net, launch2.spaceship.net |
| SOA | 1 | launch1.spaceship.net support.spaceship. |
Analysis
IP Addresses
prophp.com resolves to one IP address: 15.197.162.184.
climaterally.org, aszets.com, daytonabeachgetaway.com and two other host names share IP numbers with prophp.com.
Name Servers
prophp.com has two authoritative name servers — launch1.spaceship.net and launch2.spaceship.net.
prophp.com uses the same name servers as several other domains — among them sbep.org, elektrakom.com, acnes.org and two more.
The name servers for prophp.com overlap at least partially with those of other domains — for example yctrade.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.