ilampoo.com - dns.ninja
ilampoo.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 154.205.84.206🇺🇸 GNET-AS9294154.205.80.0/20 | ||||||
| NS | a3.share-dns.com ⭐ ⚠️ Not in parent delegation | ||||||
| A | 172.64.53.25🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | a.share-dns.com ⚠️ Not in zone NS records | ||||||
| A | 172.64.53.25🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | b.share-dns.net ⚠️ Not in zone NS records | ||||||
| A | 172.64.52.239🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | b3.share-dns.net ⚠️ Not in parent delegation | ||||||
| A | 172.64.52.239🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| SOA | a.share-dns.commaster@share-dns.com serial=1783497652 | ||||||
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=1786243974 | ||||||
Same first word
ilampoo.com |
Similar names
DNS History
24 records (5 active, 19 former)
●NSa.share-dns.com2026-04-23 → 2026-08-09 · 3 obs
● 2026-04-23 04:19:26
● 2026-08-09 03:22:36
●NSa3.share-dns.com2026-04-23 → 2026-08-09 · 3 obs
● 2026-04-23 04:19:26
● 2026-08-09 03:22:36
●NSb.share-dns.net2026-04-23 → 2026-08-09 · 3 obs
● 2026-04-23 04:19:26
● 2026-08-09 03:22:36
●NSb3.share-dns.net2026-04-23 → 2026-08-09 · 3 obs
● 2026-04-23 04:19:26
● 2026-08-09 03:22:36
○NSjm1.dns.com2019-03-02 → 2019-03-02 · 4 obs
● 2019-03-02 08:27:48
○ 2026-04-23 04:19:26
○ 2026-08-09 03:22:36
○NSjm2.dns.com2019-03-02 → 2019-03-02 · 4 obs
● 2019-03-02 08:27:48
○ 2026-04-23 04:19:26
○ 2026-08-09 03:22:36
○NSns1.myhostadmin.net2015-07-05 → 2017-02-14 · 4 obs
● 2017-02-14 14:10:02
○ 2019-03-02 08:27:48
○ 2026-08-09 03:22:36
○NSns2.myhostadmin.net2015-07-05 → 2017-02-14 · 4 obs
● 2017-02-14 14:10:02
○ 2019-03-02 08:27:48
○ 2026-08-09 03:22:36
○NSns3.myhostadmin.net2015-07-05 → 2017-02-14 · 4 obs
● 2017-02-14 14:10:02
○ 2019-03-02 08:27:48
○ 2026-08-09 03:22:36
○NSns4.myhostadmin.net2015-07-05 → 2017-02-14 · 4 obs
● 2017-02-14 14:10:02
○ 2019-03-02 08:27:48
○ 2026-08-09 03:22:36
○NSns5.myhostadmin.net2015-07-05 → 2017-02-14 · 4 obs
● 2017-02-14 14:10:02
○ 2019-03-02 08:27:48
○ 2026-08-09 03:22:36
○NSns6.myhostadmin.net2015-07-05 → 2017-02-14 · 4 obs
● 2017-02-14 14:10:02
○ 2019-03-02 08:27:48
○ 2026-08-09 03:22:36
○MXmail.ilampoo.com2015-07-05 → 2016-05-06 · 4 obs
● 2016-05-06 15:47:50
○ 2017-02-14 14:10:02
○ 2026-08-09 03:22:36
○MXmail.ilampoo.com.ilampoo.com2017-02-14 → 2017-02-14 · 4 obs
● 2017-02-14 14:10:02
○ 2019-03-02 08:27:48
○ 2026-08-09 03:22:36
○MXmx1.myhostadmin.net2017-02-14 → 2017-02-14 · 4 obs
● 2017-02-14 14:10:02
○ 2019-03-02 08:27:48
○ 2026-08-09 03:22:36
○MXoversea.800cdn.com2015-07-05 → 2016-05-06 · 4 obs
● 2016-05-06 15:47:50
○ 2017-02-14 14:10:02
○ 2026-08-09 03:22:36
○MXoversea.800cdn.com.ilampoo.com2017-02-14 → 2017-02-14 · 4 obs
● 2017-02-14 14:10:02
○ 2019-03-02 08:27:48
○ 2026-08-09 03:22:36
○MXoversea2.800cdn.com2015-07-05 → 2016-05-06 · 4 obs
● 2016-05-06 15:47:50
○ 2017-02-14 14:10:02
○ 2026-08-09 03:22:36
○A154.205.83.2102026-04-23 → 2026-04-23 · 4 obs
● 2026-04-23 04:19:26
○ 2026-05-01 10:32:54
○ 2026-08-09 03:22:36
●A154.205.84.2062026-05-01 → 2026-08-09 · 3 obs
● 2026-05-01 10:32:54
● 2026-08-09 03:22:36
○A154.222.49.942019-03-02 → 2019-03-02 · 4 obs
● 2019-03-02 08:27:48
○ 2026-04-23 04:19:26
○ 2026-08-09 03:22:36
○A23.234.27.722017-02-14 → 2017-02-14 · 3 obs
○ 2019-03-02 08:27:48
○ 2026-08-09 03:22:36
○CNAMElzyy25603.gotoip3.com2017-02-14 → 2017-02-14 · 3 obs
○ 2019-03-02 08:27:48
○ 2026-08-09 03:22:36
○CNAMEweb.m83.vhostgo.com2017-02-14 → 2017-02-14 · 3 obs
○ 2019-03-02 08:27:48
○ 2026-08-09 03:22:36
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | m.gtld-servers.net, e.gtld-servers.net, h.gtld-servers.net, a.gtld-servers.net... | - |
| ilampoo.com | b3.share-dns.net, a3.share-dns.com | 1 record |
✅ Authoritative Response
Server:172.64.53.25
NS records: b3.share-dns.net, a3.share-dns.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for ilampoo.com (unsigned zone)
⏱️ Timing
Total: 340ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 154.205.84.206 |
| NS | 2 | a.share-dns.com, b.share-dns.net |
| SOA | 1 | a.share-dns.com master.share-dns.com |
📌 Glue Records Collected
Total: 1
Out-of-bailiwick: 1 (a3.share-dns.com)
Analysis
IP Addresses
ilampoo.com points to a single IP number: 154.205.84.206.
Additional host names — bscp288.com, www.lm44x.com, bfball.cc and two others — share IP numbers with ilampoo.com.
Name Servers
ilampoo.com has four authoritative name servers: a3.share-dns.com, a.share-dns.com, b3.share-dns.net and b.share-dns.net.
At least some of ilampoo.com's name servers are shared with other domains, for example birpit.com, tntreloading.com, jinsuibao.com and two more.
These name servers tend to co-occur with a6.share-dns.com, b6.share-dns.net, a4.share-dns.com and 7 other name servers in the same DNS delegations.
a3.share-dns.com and a.share-dns.com each resolve to 172.64.53.25, while b3.share-dns.net and b.share-dns.net each resolve to 172.64.52.239.
a3.share-dns.com and a.share-dns.com are host names that each point to 172.64.53.25 IP addresses.
b3.share-dns.net and b.share-dns.net are host names that each point to 172.64.52.239 IP addresses.