angelosferranteesq.com - robtex.com
angelosferranteesq.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | parking1.mdnsservice.com ⚠️ Not in zone NS records | ||||||
| A | 2604:4000:0:d:64:99:97:39🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000 | ||||||
| PTR | parking1.mdnsservice.com | ||||||
| A | 64.99.97.39🇨🇦 TUCOWS64.99.97.0/24 -BRA-BLK2.7.4 | ||||||
| PTR | parking1.mdnsservice.com | ||||||
| NS | parking2.mdnsservice.com ⚠️ Not in zone NS records | ||||||
| A | 2604:4000:2800:d:64:99:148:19🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co. | ||||||
| PTR | parking2.mdnsservice.com | ||||||
| A | 64.98.148.19🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co. | ||||||
| PTR | parking2.mdnsservice.com | ||||||
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=1775319732 | ||||||
Same first word
angelosferranteesq.com |
DNS History
14 records (2 active, 12 former)
○NSdns022.a.register.com2016-03-11 → 2016-07-04 · 5 obs
○ 2015-12-01 00:30:56
● 2016-03-11 00:13:50
● 2016-07-04 05:58:28
○ 2026-04-03 11:39:22
○ 2026-04-04 16:50:22
● 2016-03-11 00:13:50
● 2016-07-04 05:58:28
○ 2026-04-03 11:39:22
○ 2026-04-04 16:50:22
○NSdns082.d.register.com2016-03-11 → 2016-07-04 · 5 obs
○ 2015-12-01 00:30:56
● 2016-03-11 00:13:50
● 2016-07-04 05:58:28
○ 2026-04-03 11:39:22
○ 2026-04-04 16:50:22
● 2016-03-11 00:13:50
● 2016-07-04 05:58:28
○ 2026-04-03 11:39:22
○ 2026-04-04 16:50:22
○NSdns1.registeredsite.com2015-08-05 → 2015-12-01 · 4 obs
● 2015-08-05 22:17:44
● 2015-12-01 00:30:56
○ 2016-03-11 00:13:50
○ 2026-04-04 16:50:22
● 2015-12-01 00:30:56
○ 2016-03-11 00:13:50
○ 2026-04-04 16:50:22
○NSdns2.registeredsite.com2015-08-05 → 2015-12-01 · 4 obs
● 2015-08-05 22:17:44
● 2015-12-01 00:30:56
○ 2016-03-11 00:13:50
○ 2026-04-04 16:50:22
● 2015-12-01 00:30:56
○ 2016-03-11 00:13:50
○ 2026-04-04 16:50:22
○NSdns228.b.register.com2016-03-11 → 2016-07-04 · 5 obs
○ 2015-12-01 00:30:56
● 2016-03-11 00:13:50
● 2016-07-04 05:58:28
○ 2026-04-03 11:39:22
○ 2026-04-04 16:50:22
● 2016-03-11 00:13:50
● 2016-07-04 05:58:28
○ 2026-04-03 11:39:22
○ 2026-04-04 16:50:22
○NSdns241.c.register.com2016-03-11 → 2016-07-04 · 5 obs
○ 2015-12-01 00:30:56
● 2016-03-11 00:13:50
● 2016-07-04 05:58:28
○ 2026-04-03 11:39:22
○ 2026-04-04 16:50:22
● 2016-03-11 00:13:50
● 2016-07-04 05:58:28
○ 2026-04-03 11:39:22
○ 2026-04-04 16:50:22
○NSdns3.registeredsite.com2015-08-05 → 2015-12-01 · 4 obs
● 2015-08-05 22:17:44
● 2015-12-01 00:30:56
○ 2016-03-11 00:13:50
○ 2026-04-04 16:50:22
● 2015-12-01 00:30:56
○ 2016-03-11 00:13:50
○ 2026-04-04 16:50:22
●NSparking1.mdnsservice.com2026-04-03 → 2026-04-04 · 3 obs
○ 2016-07-04 05:58:28
● 2026-04-03 11:39:22
● 2026-04-04 16:50:22
● 2026-04-03 11:39:22
● 2026-04-04 16:50:22
●NSparking2.mdnsservice.com2026-04-03 → 2026-04-04 · 3 obs
○ 2016-07-04 05:58:28
● 2026-04-03 11:39:22
● 2026-04-04 16:50:22
● 2026-04-03 11:39:22
● 2026-04-04 16:50:22
○MXinbound.registeredsite.com2015-08-05 → 2015-12-01 · 4 obs
● 2015-08-05 22:17:44
● 2015-12-01 00:30:56
○ 2016-03-11 00:13:50
○ 2026-04-04 16:50:22
● 2015-12-01 00:30:56
○ 2016-03-11 00:13:50
○ 2026-04-04 16:50:22
○MXp.webcom.ctmail.com2016-07-04 → 2016-07-04 · 4 obs
○ 2016-03-11 00:13:50
● 2016-07-04 05:58:28
○ 2026-04-03 11:39:22
○ 2026-04-04 16:50:22
● 2016-07-04 05:58:28
○ 2026-04-03 11:39:22
○ 2026-04-04 16:50:22
○A104.209.136.2332016-03-11 → 2016-07-04 · 5 obs
○ 2015-12-01 00:30:56
● 2016-03-11 00:13:50
● 2016-07-04 05:58:28
○ 2026-04-03 11:39:22
○ 2026-04-04 16:50:22
● 2016-03-11 00:13:50
● 2016-07-04 05:58:28
○ 2026-04-03 11:39:22
○ 2026-04-04 16:50:22
○A191.239.58.432016-03-11 → 2016-07-04 · 5 obs
○ 2015-12-01 00:30:56
● 2016-03-11 00:13:50
● 2016-07-04 05:58:28
○ 2026-04-03 11:39:22
○ 2026-04-04 16:50:22
● 2016-03-11 00:13:50
● 2016-07-04 05:58:28
○ 2026-04-03 11:39:22
○ 2026-04-04 16:50:22
○A209.237.150.202015-08-05 → 2015-12-01 · 4 obs
● 2015-08-05 22:17:44
● 2015-12-01 00:30:56
○ 2016-03-11 00:13:50
○ 2026-04-04 16:50:22
● 2015-12-01 00:30:56
○ 2016-03-11 00:13:50
○ 2026-04-04 16:50:22
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, g.gtld-servers.net, i.gtld-servers.net, k.gtld-servers.net... | - |
| angelosferranteesq.com | parking1.mdnsservice.com, parking2.mdnsservice.com | 2 records |
✅ Authoritative Response
Server:64.98.148.19
NS records: parking1.mdnsservice.com, parking2.mdnsservice.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for angelosferranteesq.com (unsigned zone)
⏱️ Timing
Total: 157ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (parking1.mdnsservice.com, parking2.mdnsservice.com)
Analysis
Name Servers
angelosferranteesq.com's delegation is to two name servers parking1.mdnsservice.com and parking2.mdnsservice.com.
angelosferranteesq.com shares the same name server configuration as other domains, such as saudi-web.com, reliancetransferboards.com, dealsonting.com, mynetstor.net and machinetoolsnetwork.com.
Host names with two IP numbers: parking1.mdnsservice.com points to 2604:4000:0:d:64:99:97:39 and 64.99.97.39; parking2.mdnsservice.com points to 2604:4000:2800:d:64:99:148:19 and 64.98.148.19