pulsecams.com - robtex.com
pulsecams.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 | 3d748f86-1c1b-4696-a763-c50b64f9d9db | ||||||
| SOA | launch1.spaceship.netsupport@spaceship.com serial=1772558648 | ||||||
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=1775984962 | ||||||
Previously MX for
pulsecams.com |
Same first word
pulsecams.com |
Similar names
eslcampus.com |
sacemplus.com |
sumsplace.ca |
scampulse.com |
plumcases.com |
salmescup.com |
musclespa.com |
upscalems.com |
scelusmap.com |
DNS History
16 records (4 active, 12 former)
○NSdns1.registrar-servers.com2016-09-18 → 2016-09-18 · 3 obs
● 2016-09-18 02:01:36
○ 2017-04-10 09:56:24
○ 2026-04-12 09:18:12
○ 2017-04-10 09:56:24
○ 2026-04-12 09:18:12
○NSdns2.registrar-servers.com2016-09-18 → 2016-09-18 · 3 obs
● 2016-09-18 02:01:36
○ 2017-04-10 09:56:24
○ 2026-04-12 09:18:12
○ 2017-04-10 09:56:24
○ 2026-04-12 09:18:12
●NSlaunch1.spaceship.net2026-04-07 → 2026-04-12 · 3 obs
○ 2017-04-10 09:56:24
● 2026-04-07 14:50:38
● 2026-04-12 09:18:12
● 2026-04-07 14:50:38
● 2026-04-12 09:18:12
●NSlaunch2.spaceship.net2026-04-07 → 2026-04-12 · 3 obs
○ 2017-04-10 09:56:24
● 2026-04-07 14:50:38
● 2026-04-12 09:18:12
● 2026-04-07 14:50:38
● 2026-04-12 09:18:12
○NSns513682.ip-167-114-158.net2017-04-10 → 2017-04-10 · 4 obs
○ 2016-09-18 02:01:36
● 2017-04-10 09:56:24
○ 2026-04-07 14:50:38
○ 2026-04-12 09:18:12
● 2017-04-10 09:56:24
○ 2026-04-07 14:50:38
○ 2026-04-12 09:18:12
○NSsdns1.ovh.ca2017-04-10 → 2017-04-10 · 4 obs
○ 2016-09-18 02:01:36
● 2017-04-10 09:56:24
○ 2026-04-07 14:50:38
○ 2026-04-12 09:18:12
● 2017-04-10 09:56:24
○ 2026-04-07 14:50:38
○ 2026-04-12 09:18:12
○MXeforward1.registrar-servers.com2016-09-18 → 2016-09-18 · 3 obs
● 2016-09-18 02:01:36
○ 2017-04-10 09:56:24
○ 2026-04-12 09:18:12
○ 2017-04-10 09:56:24
○ 2026-04-12 09:18:12
○MXeforward2.registrar-servers.com2016-09-18 → 2016-09-18 · 3 obs
● 2016-09-18 02:01:36
○ 2017-04-10 09:56:24
○ 2026-04-12 09:18:12
○ 2017-04-10 09:56:24
○ 2026-04-12 09:18:12
○MXeforward3.registrar-servers.com2016-09-18 → 2016-09-18 · 3 obs
● 2016-09-18 02:01:36
○ 2017-04-10 09:56:24
○ 2026-04-12 09:18:12
○ 2017-04-10 09:56:24
○ 2026-04-12 09:18:12
○MXeforward4.registrar-servers.com2016-09-18 → 2016-09-18 · 3 obs
● 2016-09-18 02:01:36
○ 2017-04-10 09:56:24
○ 2026-04-12 09:18:12
○ 2017-04-10 09:56:24
○ 2026-04-12 09:18:12
○MXeforward5.registrar-servers.com2016-09-18 → 2016-09-18 · 3 obs
● 2016-09-18 02:01:36
○ 2017-04-10 09:56:24
○ 2026-04-12 09:18:12
○ 2017-04-10 09:56:24
○ 2026-04-12 09:18:12
○MXpulsecams.com2017-04-10 → 2017-04-10 · 4 obs
○ 2016-09-18 02:01:36
● 2017-04-10 09:56:24
○ 2026-04-07 14:50:38
○ 2026-04-12 09:18:12
● 2017-04-10 09:56:24
○ 2026-04-07 14:50:38
○ 2026-04-12 09:18:12
○A162.255.119.2502016-09-18 → 2016-09-18 · 3 obs
● 2016-09-18 02:01:36
○ 2017-04-10 09:56:24
○ 2026-04-12 09:18:12
○ 2017-04-10 09:56:24
○ 2026-04-12 09:18:12
○A167.114.158.522017-04-10 → 2017-04-10 · 4 obs
○ 2016-09-18 02:01:36
● 2017-04-10 09:56:24
○ 2026-04-07 14:50:38
○ 2026-04-12 09:18:12
● 2017-04-10 09:56:24
○ 2026-04-07 14:50:38
○ 2026-04-12 09:18:12
●A44.232.173.2492026-04-07 → 2026-04-12 · 3 obs
○ 2017-04-10 09:56:24
● 2026-04-07 14:50:38
● 2026-04-12 09:18:12
● 2026-04-07 14:50:38
● 2026-04-12 09:18:12
●A52.40.42.1132026-04-07 → 2026-04-12 · 3 obs
○ 2017-04-10 09:56:24
● 2026-04-07 14:50:38
● 2026-04-12 09:18:12
● 2026-04-07 14:50:38
● 2026-04-12 09:18:12
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | m.gtld-servers.net, d.gtld-servers.net, a.gtld-servers.net, f.gtld-servers.net... | - |
| pulsecams.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 pulsecams.com (unsigned zone)
⏱️ Timing
Total: 701ms | 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 | 3d748f86-1c1b-4696-a763-c50b64f9d9db |
| SOA | 1 | launch1.spaceship.net support.spaceship. |
Analysis
IP Addresses
pulsecams.com points to two IP numbers: 44.232.173.249 and 52.40.42.113.
Other host names such as f8dy.com, sa.tc, craval.com, anntour.com and barcuda.com share IPs with pulsecams.com.
Name Servers
pulsecams.com is delegated to two name servers: launch1.spaceship.net and launch2.spaceship.net.
pulsecams.com shares the same name server setup as lanchesterparish.info, tahio.com, betgacor.com, jmtop.com and tokyo.tips.
Host names with two IP numbers: launch1.spaceship.net points to: 2400:cb00:2049:1::a29f:1a26 and 162.159.26.38; launch2.spaceship.net points to: 2400:cb00:2049:1::a29f:1b20 and 162.159.27.32.