leadapi.net - dns.ninja

leadapi.net

DNSSEC⚠️ Not signed
A18.223.103.187🇺🇸 Amazon18.220.0.0/14 EC2 CMH prefix
PTRec2-18-223-103-187.us-east-2.compute.amazonaws.com
NSdns1.registrar-servers.com ⭐
A2610:a1:1024::200🇺🇸 MAINT-ID-120082610:a1:1024::/48 Neustar
PTRdns1.namecheaphosting.com
PTRdns1.registrar-servers.com
A156.154.132.200🇺🇸 MAINT-ID-12008156.154.132.0/24 Neustar
PTRdns1.namecheaphosting.com
PTRdns1.registrar-servers.com
NSdns2.registrar-servers.com
A2610:a1:1025::200🇺🇸 MAINT-ID-120082610:a1:1025::/48 Neustar
PTRdns2.namecheaphosting.com
PTRdns2.registrar-servers.com
A156.154.133.200🇺🇸 MAINT-ID-12008156.154.133.0/24 Neustar
PTRdns2.namecheaphosting.com
PTRdns2.registrar-servers.com
MXmx.yandex.ru ⭐
A2a02:6b8::311🇷🇺 TELETECH2a02:6b8::/32 Yandex network
PTRmxfront.stable.qloud-b.yandex.net
A77.88.21.249🇷🇺 TELETECH77.88.0.0/18 Yandex enterprise network
PTRmxfront.stable.qloud-b.yandex.net
TXTrhci7israp3l4aklidsattstcg
TXTv=spf1 redirect=_spf.yandex.net
SOAdns1.registrar-servers.comhostmaster@registrar-servers.com serial=1767973054

net

DNSSEC🔒 Signed (DS record present)
NSa.gtld-servers.net ⭐
NSb.gtld-servers.net
NSc.gtld-servers.net
NSd.gtld-servers.net
NSe.gtld-servers.net
NSf.gtld-servers.net
NSg.gtld-servers.net
NSh.gtld-servers.net
NSi.gtld-servers.net
NSj.gtld-servers.net
NSk.gtld-servers.net
NSl.gtld-servers.net
NSm.gtld-servers.net
SOAa.gtld-servers.netnstld@verisign-grs.com serial=1786690824
WOT: SAFE (42/100)

Subdomains

cp.leadapi.net

Same first word

leadapi.net
leadapi.xyz
leadapi.dev

Similar names

pedalia.com
elapida.com
idealap.hu
adelpia.net
apilead.com
daipale.com
adelpia.com
pleiada.ro
padelia.com
pedalia.cc
dealapi.com
lapidea.de
lapieda.com
epilada.ch
paledia.com
pedaali.fi
dealapi.xyz
aapleid.com
aidepla.com
alpedia.net
alpedia.es
alpedia.com
pedalai.com
elapida.fr
alpedia.de
elapida.net
lapedia.net
aipedal.com
leapaid.com
alipade.com
adalipe.es

DNS History

17 records (4 active, 13 former)

2008201020122014201620182020202220242026NSdns1.registrar-servers.comdns2.registrar-servers.comdns3.registrar-servers.comdns4.registrar-servers.comdns5.registrar-servers.comns1.domainservice.comns1.trafficclub.comns2.domainservice.comns2.trafficclub.comns3.domainservice.comns3.trafficclub.comns4.domainservice.comns4.trafficclub.comMXmx.yandex.ruA18.223.103.187192.99.39.73208.79.78.230
●NSdns1.registrar-servers.com2015-06-18 → 2026-08-14 · 3 obs
○ 2007-10-20 03:07:08
● 2015-06-18 04:03:40
● 2026-08-14 07:26:38
●NSdns2.registrar-servers.com2015-11-06 → 2026-08-14 · 3 obs
○ 2015-06-18 04:03:40
● 2015-11-06 15:16:50
● 2026-08-14 07:26:38
○NSdns3.registrar-servers.com2015-11-06 → 2017-05-18 · 5 obs
○ 2015-06-18 04:03:40
● 2015-11-06 15:16:50
● 2017-05-18 13:52:32
○ 2026-02-15 06:20:38
○ 2026-08-14 07:26:38
○NSdns4.registrar-servers.com2015-11-06 → 2017-05-18 · 5 obs
○ 2015-06-18 04:03:40
● 2015-11-06 15:16:50
● 2017-05-18 13:52:32
○ 2026-02-15 06:20:38
○ 2026-08-14 07:26:38
○NSdns5.registrar-servers.com2015-11-06 → 2017-05-18 · 5 obs
○ 2015-06-18 04:03:40
● 2015-11-06 15:16:50
● 2017-05-18 13:52:32
○ 2026-02-15 06:20:38
○ 2026-08-14 07:26:38
○NSns1.domainservice.com2007-10-20 → 2007-10-20 · 3 obs
● 2007-10-20 03:07:08
○ 2015-06-18 04:03:40
○ 2026-08-14 07:26:38
○NSns1.trafficclub.com2007-10-20 → 2007-10-20 · 3 obs
● 2007-10-20 03:07:08
○ 2015-06-18 04:03:40
○ 2026-08-14 07:26:38
○NSns2.domainservice.com2007-10-20 → 2007-10-20 · 3 obs
● 2007-10-20 03:07:08
○ 2015-06-18 04:03:40
○ 2026-08-14 07:26:38
○NSns2.trafficclub.com2007-10-20 → 2007-10-20 · 3 obs
● 2007-10-20 03:07:08
○ 2015-06-18 04:03:40
○ 2026-08-14 07:26:38
○NSns3.domainservice.com2007-10-20 → 2007-10-20 · 3 obs
● 2007-10-20 03:07:08
○ 2015-06-18 04:03:40
○ 2026-08-14 07:26:38
○NSns3.trafficclub.com2007-10-20 → 2007-10-20 · 3 obs
● 2007-10-20 03:07:08
○ 2015-06-18 04:03:40
○ 2026-08-14 07:26:38
○NSns4.domainservice.com2007-10-20 → 2007-10-20 · 3 obs
● 2007-10-20 03:07:08
○ 2015-06-18 04:03:40
○ 2026-08-14 07:26:38
○NSns4.trafficclub.com2007-10-20 → 2007-10-20 · 3 obs
● 2007-10-20 03:07:08
○ 2015-06-18 04:03:40
○ 2026-08-14 07:26:38
●MXmx.yandex.ru2015-06-18 → 2026-08-14 · 3 obs
○ 2007-10-20 03:07:08
● 2015-06-18 04:03:40
● 2026-08-14 07:26:38
●A18.223.103.1872026-02-15 → 2026-08-14 · 3 obs
○ 2017-05-18 13:52:32
● 2026-02-15 06:20:38
● 2026-08-14 07:26:38
○A192.99.39.732015-06-18 → 2017-05-18 · 5 obs
○ 2007-10-20 03:07:08
● 2015-06-18 04:03:40
● 2017-05-18 13:52:32
○ 2026-02-15 06:20:38
○ 2026-08-14 07:26:38
○A208.79.78.2302007-10-20 → 2007-10-20 · 3 obs
● 2007-10-20 03:07:08
○ 2015-06-18 04:03:40
○ 2026-08-14 07:26:38

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
neta.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
leadapi.netdns1.registrar-servers.com, dns2.registrar-servers.com-

✅ Authoritative Response

Server:156.154.132.200

NS records: dns1.registrar-servers.com, dns2.registrar-servers.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for leadapi.net (unsigned zone)

⏱️ Timing

Total: 330ms | Queries: -

📄 Records

TypeCountSample Data
A118.223.103.187
NS2dns1.registrar-servers.com, dns2.registrar-servers.com
MX1mx.yandex.ru (pri: 10)
TXT2rhci7israp3l4aklidsattstcg, v=spf1 redirect=_spf.yandex.net
SOA1dns1.registrar-servers.com hostmaster.re

Analysis

Hierarchy

leadapi.net is the parent zone for cp.leadapi.net.

IP Addresses

leadapi.net directs to one IP number, which is 18.223.103.187.

Among the host names that share IP numbers with leadapi.net is ec2-18-223-103-187.us-east-2.compute.amazonaws.com, as one example.

Name Servers

The NS records for leadapi.net delegate to dns1.registrar-servers.com and dns2.registrar-servers.com.

leadapi.net has the same name server delegation as a number of other domains, such as maisonlegrand.com, hairface.net, spiraloid.net and two more.

Some of leadapi.net's name servers are also used by other domains, including sonserve.com, ravelpay.com, ticovip.com and areaexp.net.

These name servers regularly co-occur with the name servers dns3.registrar-servers.com, dns4.registrar-servers.com and dns5.registrar-servers.com.

dns1.registrar-servers.com resolves to 156.154.132.200 and 2610:a1:1024::200. Likewise, dns2.registrar-servers.com resolves to 156.154.133.200 and 2610:a1:1025::200 — two IP addresses apiece.

Mail Servers

leadapi.net routes its mail through a single mail server, mx.yandex.ru.

leadapi.net has the same mail server arrangement as a number of other domains, for example 4ll.ru, ntoa.ru, mediafabric.ru and two more.

The MX records for leadapi.net are at least partially shared with other domains, such as kuboris.ru, sheng-wang.ru, nicefactory.ru and papaasap.com.

It is common to find these mail servers paired with the mail servers mx.yandex.net.

The host mx.yandex.ru resolves to 77.88.21.249 and 2a02:6b8::311 — two IP addresses.