tecipay.com - dns.ninja
tecipay.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 | 2dc16fa0-914b-44e8-88b5-d951dc771eef | ||||||
| SOA | launch1.spaceship.netsupport@spaceship.com serial=1781287407 | ||||||
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=1786171364 | ||||||
Same first word
tecipay.com |
Similar names
ipaytec.com |
cetyapi.com.tr |
apecity.com |
paytice.com |
cetyapi.com |
etypica.com |
aetypic.com |
epacity.nl |
yeticap.com |
cityape.de |
epacity.com |
cityape.com |
citepay.com |
epacity.be |
peacity.com |
DNS History
17 records (4 active, 13 former)
○NSdns1.registrar-servers.com2019-01-18 → 2019-01-18 · 3 obs
● 2019-01-18 00:45:06
○ 2026-02-20 08:24:02
○ 2026-08-08 07:00:26
○ 2026-02-20 08:24:02
○ 2026-08-08 07:00:26
○NSdns101.registrar-servers.com2026-02-20 → 2026-02-20 · 4 obs
○ 2019-01-18 00:45:06
● 2026-02-20 08:24:02
○ 2026-03-29 03:09:02
○ 2026-08-08 07:00:26
● 2026-02-20 08:24:02
○ 2026-03-29 03:09:02
○ 2026-08-08 07:00:26
○NSdns102.registrar-servers.com2026-02-20 → 2026-02-20 · 4 obs
○ 2019-01-18 00:45:06
● 2026-02-20 08:24:02
○ 2026-03-29 03:09:02
○ 2026-08-08 07:00:26
● 2026-02-20 08:24:02
○ 2026-03-29 03:09:02
○ 2026-08-08 07:00:26
○NSdns2.registrar-servers.com2019-01-18 → 2019-01-18 · 3 obs
● 2019-01-18 00:45:06
○ 2026-02-20 08:24:02
○ 2026-08-08 07:00:26
○ 2026-02-20 08:24:02
○ 2026-08-08 07:00:26
●NSlaunch1.spaceship.net2026-04-28 → 2026-08-08 · 3 obs
○ 2026-03-29 03:09:02
● 2026-04-28 18:48:38
● 2026-08-08 07:00:26
● 2026-04-28 18:48:38
● 2026-08-08 07:00:26
●NSlaunch2.spaceship.net2026-04-28 → 2026-08-08 · 3 obs
○ 2026-03-29 03:09:02
● 2026-04-28 18:48:38
● 2026-08-08 07:00:26
● 2026-04-28 18:48:38
● 2026-08-08 07:00:26
○MXeforward1.registrar-servers.com2019-01-18 → 2019-01-18 · 3 obs
● 2019-01-18 00:45:06
○ 2026-02-20 08:24:02
○ 2026-08-08 07:00:26
○ 2026-02-20 08:24:02
○ 2026-08-08 07:00:26
○MXeforward2.registrar-servers.com2019-01-18 → 2019-01-18 · 3 obs
● 2019-01-18 00:45:06
○ 2026-02-20 08:24:02
○ 2026-08-08 07:00:26
○ 2026-02-20 08:24:02
○ 2026-08-08 07:00:26
○MXeforward3.registrar-servers.com2019-01-18 → 2019-01-18 · 3 obs
● 2019-01-18 00:45:06
○ 2026-02-20 08:24:02
○ 2026-08-08 07:00:26
○ 2026-02-20 08:24:02
○ 2026-08-08 07:00:26
○MXeforward4.registrar-servers.com2019-01-18 → 2019-01-18 · 3 obs
● 2019-01-18 00:45:06
○ 2026-02-20 08:24:02
○ 2026-08-08 07:00:26
○ 2026-02-20 08:24:02
○ 2026-08-08 07:00:26
○MXeforward5.registrar-servers.com2019-01-18 → 2019-01-18 · 3 obs
● 2019-01-18 00:45:06
○ 2026-02-20 08:24:02
○ 2026-08-08 07:00:26
○ 2026-02-20 08:24:02
○ 2026-08-08 07:00:26
○MXmx.plingest.com2026-02-20 → 2026-02-20 · 4 obs
○ 2019-01-18 00:45:06
● 2026-02-20 08:24:02
○ 2026-03-29 03:09:02
○ 2026-08-08 07:00:26
● 2026-02-20 08:24:02
○ 2026-03-29 03:09:02
○ 2026-08-08 07:00:26
○A172.234.24.2112026-02-20 → 2026-02-20 · 4 obs
○ 2019-01-18 00:45:06
● 2026-02-20 08:24:02
○ 2026-03-29 03:09:02
○ 2026-08-08 07:00:26
● 2026-02-20 08:24:02
○ 2026-03-29 03:09:02
○ 2026-08-08 07:00:26
○A172.239.57.1172026-02-20 → 2026-02-20 · 4 obs
○ 2019-01-18 00:45:06
● 2026-02-20 08:24:02
○ 2026-03-29 03:09:02
○ 2026-08-08 07:00:26
● 2026-02-20 08:24:02
○ 2026-03-29 03:09:02
○ 2026-08-08 07:00:26
○A178.237.46.432019-01-18 → 2019-01-18 · 3 obs
● 2019-01-18 00:45:06
○ 2026-02-20 08:24:02
○ 2026-08-08 07:00:26
○ 2026-02-20 08:24:02
○ 2026-08-08 07:00:26
●A44.232.173.2492026-04-28 → 2026-08-08 · 3 obs
○ 2026-03-29 03:09:02
● 2026-04-28 18:48:38
● 2026-08-08 07:00:26
● 2026-04-28 18:48:38
● 2026-08-08 07:00:26
●A52.40.42.1132026-04-28 → 2026-08-08 · 3 obs
○ 2026-03-29 03:09:02
● 2026-04-28 18:48:38
● 2026-08-08 07:00:26
● 2026-04-28 18:48:38
● 2026-08-08 07:00:26
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| tecipay.com | launch2.spaceship.net, launch1.spaceship.net | - |
✅ Authoritative Response
Server:162.159.27.32
NS records: launch2.spaceship.net, launch1.spaceship.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for tecipay.com (unsigned zone)
⏱️ Timing
Total: 1027ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 52.40.42.113, 44.232.173.249 |
| NS | 2 | launch1.spaceship.net, launch2.spaceship.net |
| TXT | 1 | 2dc16fa0-914b-44e8-88b5-d951dc771eef |
| SOA | 1 | launch1.spaceship.net support.spaceship. |
Analysis
IP Addresses
tecipay.com has two IP addresses: 44.232.173.249 and 52.40.42.113
Among the host names that share IP numbers with tecipay.com are (0x626c6f776a6f62)blonde.com, fanz.ca, meterco.com and two others.
Name Servers
The NS records for tecipay.com delegate to launch1.spaceship.net and launch2.spaceship.net.
tecipay.com has the same name server delegation as a number of other domains, such as fo76ledger.online, limitedsolution.com, corvus-tech.com and two more.
tecipay.com and other domains like danialex.com share at least a portion of their name servers.
launch1.spaceship.net resolves to 162.159.26.38 and 2400:cb00:2049:1::a29f:1a26. Likewise, launch2.spaceship.net resolves to 162.159.27.32 and 2400:cb00:2049:1::a29f:1b20 — two IP addresses apiece.