fedomar.com - dns.ninja
fedomar.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 23.111.178.102🇺🇸 HIVELOCITY-123.111.176.0/21 TPA2 Facility IPv4 Assignments | ||||||
| PTR | cp20.intodomain.com | ||||||
| NS | ns11.cp20.intodomain.net ⭐ ⚠️ Not in parent delegation | ||||||
| A | 23.111.175.181🇺🇸 HIVELOCITY-123.111.160.0/20 TPA2 Secondary IP Space Assignment | ||||||
| PTR | s20.intodomain.com | ||||||
| NS | ns1.s20.intodomain.net ⚠️ Not in zone NS records | ||||||
| A | 23.111.175.181🇺🇸 HIVELOCITY-123.111.160.0/20 TPA2 Secondary IP Space Assignment | ||||||
| PTR | s20.intodomain.com | ||||||
| NS | ns12.cp20.intodomain.net ⚠️ Not in parent delegation | ||||||
| A | 23.111.175.182🇺🇸 HIVELOCITY-123.111.160.0/20 TPA2 Secondary IP Space Assignment | ||||||
| PTR | s20.intodomain.com | ||||||
| NS | ns2.s20.intodomain.net ⚠️ Not in zone NS records | ||||||
| A | 23.111.175.182🇺🇸 HIVELOCITY-123.111.160.0/20 TPA2 Secondary IP Space Assignment | ||||||
| PTR | s20.intodomain.com | ||||||
| MX | fedomar.com ⭐ | ||||||
| A | 23.111.178.102🇺🇸 HIVELOCITY-123.111.176.0/21 TPA2 Facility IPv4 Assignments | ||||||
| PTR | cp20.intodomain.com | ||||||
| TXT | v=spf1 ip4:23.111.178.102 ip4:23.111.136.182 ip4:217.79.248.34 ip4:23.111.175... | ||||||
| SOA | ns11.cp20.intodomain.netinfo@host.com.do 2026-07-27 #4 | ||||||
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=1786710114 | ||||||
MX for
fedomar.com |
Same first word
fedomar.com |
Similar names
DNS History
24 records (6 active, 18 former)
○NScp1.grupohost.net2015-08-11 → 2017-03-28 · 7 obs
● 2016-01-16 00:25:10
○ 2016-04-21 06:45:02
○ 2016-06-19 17:06:50
● 2017-03-28 14:14:56
○ 2017-07-07 07:16:22
○ 2026-08-14 12:50:42
○NScp10.grupohost.net2016-04-21 → 2017-03-28 · 5 obs
● 2016-04-21 06:45:02
● 2017-03-28 14:14:56
○ 2017-07-07 07:16:22
○ 2026-08-14 12:50:42
○NScp11.grupohost.net2016-04-21 → 2017-03-28 · 5 obs
● 2016-04-21 06:45:02
● 2017-03-28 14:14:56
○ 2017-07-07 07:16:22
○ 2026-08-14 12:50:42
○NScp2.grupohost.net2015-08-11 → 2017-03-28 · 4 obs
● 2017-03-28 14:14:56
○ 2017-07-07 07:16:22
○ 2026-08-14 12:50:42
○NSdns10.parkpage.foundationapi.com2026-02-19 → 2026-02-19 · 4 obs
● 2026-02-19 22:01:26
○ 2026-03-22 19:24:02
○ 2026-08-14 12:50:42
○NSdns11.parkpage.foundationapi.com2026-02-19 → 2026-02-19 · 4 obs
● 2026-02-19 22:01:26
○ 2026-03-22 19:24:02
○ 2026-08-14 12:50:42
○NSns1.host.do.grupohost.net2017-07-07 → 2017-07-07 · 4 obs
● 2017-07-07 07:16:22
○ 2026-02-17 11:24:28
○ 2026-08-14 12:50:42
○NSns1.intodomain.net2026-02-17 → 2026-03-22 · 6 obs
● 2026-02-17 11:24:28
○ 2026-02-19 22:01:26
● 2026-03-22 19:24:02
○ 2026-08-01 13:46:04
○ 2026-08-14 12:50:42
●NSns1.s20.intodomain.net2026-02-17 → 2026-08-14 · 5 obs
● 2026-02-17 11:24:28
○ 2026-02-19 22:01:26
● 2026-03-22 19:24:02
● 2026-08-14 12:50:42
○NSns1.verification-hold.suspended-domain.com2026-02-19 → 2026-02-19 · 4 obs
● 2026-02-19 22:01:26
○ 2026-03-22 19:24:02
○ 2026-08-14 12:50:42
●NSns11.cp20.intodomain.net2026-08-01 → 2026-08-14 · 3 obs
● 2026-08-01 13:46:04
● 2026-08-14 12:50:42
●NSns12.cp20.intodomain.net2026-08-01 → 2026-08-14 · 3 obs
● 2026-08-01 13:46:04
● 2026-08-14 12:50:42
○NSns2.host.do.grupohost.net2017-07-07 → 2017-07-07 · 4 obs
● 2017-07-07 07:16:22
○ 2026-02-17 11:24:28
○ 2026-08-14 12:50:42
○NSns2.intodomain.net2026-02-17 → 2026-03-22 · 6 obs
● 2026-02-17 11:24:28
○ 2026-02-19 22:01:26
● 2026-03-22 19:24:02
○ 2026-08-01 13:46:04
○ 2026-08-14 12:50:42
●NSns2.s20.intodomain.net2026-02-17 → 2026-08-14 · 5 obs
● 2026-02-17 11:24:28
○ 2026-02-19 22:01:26
● 2026-03-22 19:24:02
● 2026-08-14 12:50:42
○NSns3.cp20.grupohost.net2017-07-07 → 2017-07-07 · 4 obs
● 2017-07-07 07:16:22
○ 2026-02-17 11:24:28
○ 2026-08-14 12:50:42
○NSns4.cp20.grupohost.net2017-07-07 → 2017-07-07 · 4 obs
● 2017-07-07 07:16:22
○ 2026-02-17 11:24:28
○ 2026-08-14 12:50:42
●MXfedomar.com2015-08-11 → 2026-08-14 · 5 obs
● 2026-02-17 11:24:28
○ 2026-02-19 22:01:26
● 2026-03-22 19:24:02
● 2026-08-14 12:50:42
○A15.197.240.202026-02-19 → 2026-02-19 · 4 obs
● 2026-02-19 22:01:26
○ 2026-03-22 19:24:02
○ 2026-08-14 12:50:42
○A162.254.145.2032017-07-07 → 2017-07-07 · 4 obs
● 2017-07-07 07:16:22
○ 2026-02-17 11:24:28
○ 2026-08-14 12:50:42
○A173.192.46.962015-08-11 → 2016-06-19 · 4 obs
● 2016-06-19 17:06:50
○ 2017-03-28 14:14:56
○ 2026-08-14 12:50:42
○A209.133.202.22017-03-28 → 2017-03-28 · 4 obs
● 2017-03-28 14:14:56
○ 2017-07-07 07:16:22
○ 2026-08-14 12:50:42
○A23.111.136.1822026-02-17 → 2026-03-22 · 6 obs
● 2026-02-17 11:24:28
○ 2026-02-19 22:01:26
● 2026-03-22 19:24:02
○ 2026-08-01 13:46:04
○ 2026-08-14 12:50:42
●A23.111.178.1022026-08-01 → 2026-08-14 · 3 obs
● 2026-08-01 13:46:04
● 2026-08-14 12:50:42
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | e.gtld-servers.net, h.gtld-servers.net, j.gtld-servers.net, b.gtld-servers.net... | - |
| fedomar.com | ns1.s20.intodomain.net, ns2.s20.intodomain.net | - |
✅ Authoritative Response
Server:23.111.175.181
NS records: ns1.s20.intodomain.net, ns2.s20.intodomain.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for fedomar.com (unsigned zone)
⏱️ Timing
Total: 428ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 23.111.178.102 |
| NS | 2 | ns12.cp20.intodomain.net, ns11.cp20.intodomain.net |
| MX | 1 | fedomar.com (pri: 0) |
| TXT | 1 | v=spf1 ip4:23.111.178.102 ip4:23.111.136 |
| SOA | 1 | ns11.cp20.intodomain.net info.host.com.d |
Analysis
Mail Server Role
fedomar.com serves as a mail server for fedomar.com.
IP Addresses
fedomar.com has exactly one IP address — 23.111.178.102.
enaco.edu.do, cp20.intodomain.com, mail3.bdcint.com.do plus two other host names have IP numbers in common with fedomar.com.
Name Servers
Four name servers handle the delegation for fedomar.com: ns11.cp20.intodomain.net, ns12.cp20.intodomain.net, ns1.s20.intodomain.net and ns2.s20.intodomain.net.
The name servers of fedomar.com overlap at least partially with those of other domains — among them sss.com.do, hosting.com.do, powernet.hn and two more.
These name servers commonly co-occur with the name servers ns1.intodomain.net, ns2.intodomain.net, dns1.intodomain.net and dns2.intodomain.net.
Each of the host names ns11.cp20.intodomain.net, ns12.cp20.intodomain.net, ns1.s20.intodomain.net and ns2.s20.intodomain.net has one IP address: ns11.cp20.intodomain.net resolves to 23.111.175.181, ns12.cp20.intodomain.net resolves to 23.111.175.182, ns1.s20.intodomain.net resolves to 23.111.175.181 and ns2.s20.intodomain.net resolves to 23.111.175.182.
ns11.cp20.intodomain.net along with ns1.s20.intodomain.net each resolve to 23.111.175.181 IP addresses.
ns12.cp20.intodomain.net along with ns2.s20.intodomain.net each resolve to 23.111.175.182 IP addresses.
Mail Servers
fedomar.com uses exactly one mail server, which is fedomar.com.
fedomar.com carries a single IP number, which is 23.111.178.102.