mailzed.com - robtex.com
mailzed.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.idatahouse.com ⚠️ Not in zone NS records | ||||||
| A | 2a02:2068:1000:300::4🇪🇸 Equinix2a02:2068::/29 Madrid | ||||||
| A | 217.15.32.2🇪🇸 Equinix217.15.32.0/20 Madrid | ||||||
| PTR | ns1.idatahouse.com | ||||||
| NS | ns2.idatahouse.com ⚠️ Not in zone NS records | ||||||
| A | 2a02:2068:1000:300::5🇪🇸 Equinix2a02:2068::/29 Madrid | ||||||
| A | 217.15.32.34🇪🇸 Equinix217.15.32.0/20 Madrid | ||||||
| PTR | ns2.idatahouse.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=1774792432 | ||||||
Same first word
mailzed.com |
Similar names
zedmail.fr |
medzila.net |
dzemali.ch |
zedmail.co.uk |
damizle.net |
delmaiz.info |
zedmail.net |
mideazl.net |
mezaldi.com |
zedmail.de |
zimaled.com |
zialmed.com |
dezimal.de |
dezimal.com |
zedmail.com |
🔍 DNS Trace
Analysis
Name Servers
mailzed.com is delegated to two name servers: ns1.idatahouse.com and ns2.idatahouse.com.
mailzed.com uses the same name server setup as other domains, including smartclubsa.mobi and castillaclubdefutbol.org.
mailzed.com at least partially shares name servers with other domains, for instance realmadrid.net, realmadrid.jp, movilesyoigo.com, realmadrid.co.id and realmadrid.id.
These name servers are commonly used alongside pdns80.ultradns.biz, pdns80.ultradns.com, pdns80.ultradns.net, pdns80.ultradns.org, dns01.yoigo.es, dns02.yoigo.es, ns1-179.akam.net, ns1-18.akam.net, usc2.akam.net and usc4.akam.net.
Host names with two IP numbers: ns1.idatahouse.com points to: 2a02:2068:1000:300::4 and 217.15.32.2; ns2.idatahouse.com points to: 2a02:2068:1000:300::5 and 217.15.32.34.