casarosal.com - dns.ninja
casarosal.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=1784824707 | ||||||
Same first word
casarosal.com |
Similar names
casasolar.es |
lacasasro.sk |
casasolar.eu |
calarossa.com |
solarcasa.cat |
lacarossa.com.py |
solarcasa.energy |
solarcasa.com.br |
larocassa.cat |
casalaros.nl |
carosalas.com |
oscarlasa.com |
DNS History
11 records (8 active, 3 former)
○NSns1.ipage.com2015-06-29 → 2016-02-02 · 4 obs
● 2016-02-02 10:43:14
○ 2016-04-22 22:21:06
○ 2026-07-23 16:54:28
○NSns2.ipage.com2015-06-29 → 2016-02-02 · 4 obs
● 2016-02-02 10:43:14
○ 2016-04-22 22:21:06
○ 2026-07-23 16:54:28
●NSpdns07.domaincontrol.com2016-04-22 → 2026-07-23 · 3 obs
● 2016-04-22 22:21:06
● 2026-07-23 16:54:28
●NSpdns08.domaincontrol.com2016-04-22 → 2026-07-23 · 3 obs
● 2016-04-22 22:21:06
● 2026-07-23 16:54:28
●MXalt1.aspmx.l.google.com2016-04-22 → 2026-07-23 · 3 obs
● 2016-04-22 22:21:06
● 2026-07-23 16:54:28
●MXalt2.aspmx.l.google.com2016-04-22 → 2026-07-23 · 3 obs
● 2016-04-22 22:21:06
● 2026-07-23 16:54:28
●MXaspmx.l.google.com2016-04-22 → 2026-07-23 · 3 obs
● 2016-04-22 22:21:06
● 2026-07-23 16:54:28
●MXaspmx2.googlemail.com2016-04-22 → 2026-07-23 · 3 obs
● 2016-04-22 22:21:06
● 2026-07-23 16:54:28
●MXaspmx3.googlemail.com2016-04-22 → 2026-07-23 · 3 obs
● 2016-04-22 22:21:06
● 2026-07-23 16:54:28
○MXmx.ipage.com2015-06-29 → 2016-02-02 · 4 obs
● 2016-02-02 10:43:14
○ 2016-04-22 22:21:06
○ 2026-07-23 16:54:28
●A199.167.218.1022015-06-29 → 2026-07-23 · 2 obs
● 2026-07-23 16:54:28
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| casarosal.com | pdns07.domaincontrol.com, pdns08.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.79.53
NS records: pdns07.domaincontrol.com, pdns08.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for casarosal.com (unsigned zone)
⏱️ Timing
Total: 292ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 199.167.218.102 |
| NS | 2 | pdns07.domaincontrol.com, pdns08.domaincontrol.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| SOA | 1 | pdns07.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (pdns07.domaincontrol.com, pdns07.domaincontrol.com, pdns08.domaincontrol.com...)
Analysis
IP Addresses
casarosal.com resolves to just one IP address, 199.167.218.102.
Two other host names, along with mx.simsburyinn.com, crownpromenadehotel.com.au and cgh305.com, also share IP numbers with casarosal.com.
Name Servers
casarosal.com uses two name servers for its delegation: pdns07.domaincontrol.com and pdns08.domaincontrol.com.
casarosal.com shares its NS records with other domains, for example pyla.org.cy, hospitalityuniforms.net, archivonacional.org and two others.
casarosal.com and other domains like dsgtag.com, ovc.cc and exeterainfo.com share some name servers
The two host names pdns07.domaincontrol.com and pdns08.domaincontrol.com each have a pair of IP addresses: pdns07.domaincontrol.com has 97.74.111.53 and 2603:5:21f1::35, and pdns08.domaincontrol.com has 173.201.79.53 and 2603:5:22f1::35.
Mail Servers
casarosal.com is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
There is at least a partial MX overlap between casarosal.com and other domains, including ns500699.ns500734.ns500734.ns500699.ns500699.ns500699.ns500693.ns500699.ns500683.ns500683.ns500612.ns500632.ns500612.ns500612.ns500110.dtrkdll.com, ns500731.ns500731.ns500754.ns500731.ns500754.ns500671.ns500731.ns500731.ns500731.ns500671.ns500688.ns500705.ns500291.ns500291.ns500291.ns500666.tenderladiesbz.com, ns500698.ns500698.ns500758.ns500736.ns500736.ns500735.ns500735.ns500708.ns500708.ns500576.ns500576.ns500686.ns500652.ns500619.ns500619.trackreceptor.com and two others.
These mail servers tend to appear in combination with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.
Host names that have two IP addresses:
aspmx2.googlemail.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
aspmx3.googlemail.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.
aspmx.l.google.com directs traffic to 142.251.167.26 and 2607:f8b0:4004:c29::1a.
alt1.aspmx.l.google.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1b.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c0f::1a IP addresses each.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 108.177.123.26 IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 2a00:1450:400b:c02::1b IP addresses each.