midrid.com - dns.ninja
midrid.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=1786576344 | ||||||
PTR for
Subdomains
www.midrid.com |
Same first word
midrid.com |
Similar names
DNS History
25 records (8 active, 17 former)
○NSb.ns.verio.net2007-10-22 → 2007-10-22 · 3 obs
○ 2015-08-10 00:33:04
○ 2026-08-12 23:32:38
○NSdns1.p05.nsone.net2016-10-24 → 2017-08-01 · 5 obs
● 2016-10-24 13:32:30
● 2017-08-01 05:57:52
○ 2026-04-13 00:03:26
○ 2026-08-12 23:32:38
○NSdns2.p05.nsone.net2016-10-24 → 2017-08-01 · 5 obs
● 2016-10-24 13:32:30
● 2017-08-01 05:57:52
○ 2026-04-13 00:03:26
○ 2026-08-12 23:32:38
○NSdns3.p05.nsone.net2016-10-24 → 2017-08-01 · 5 obs
● 2016-10-24 13:32:30
● 2017-08-01 05:57:52
○ 2026-04-13 00:03:26
○ 2026-08-12 23:32:38
○NSdns4.p05.nsone.net2016-10-24 → 2017-08-01 · 5 obs
● 2016-10-24 13:32:30
● 2017-08-01 05:57:52
○ 2026-04-13 00:03:26
○ 2026-08-12 23:32:38
○NSns1.p05.dynect.net2015-08-10 → 2016-09-12 · 5 obs
● 2015-08-10 00:33:04
● 2016-09-12 15:00:54
○ 2016-10-24 13:32:30
○ 2026-08-12 23:32:38
○NSns2.p05.dynect.net2015-08-10 → 2016-09-12 · 5 obs
● 2015-08-10 00:33:04
● 2016-09-12 15:00:54
○ 2016-10-24 13:32:30
○ 2026-08-12 23:32:38
○NSns3.p05.dynect.net2015-08-10 → 2016-09-12 · 5 obs
● 2015-08-10 00:33:04
● 2016-09-12 15:00:54
○ 2016-10-24 13:32:30
○ 2026-08-12 23:32:38
●NSns33.domaincontrol.com2026-04-13 → 2026-08-12 · 3 obs
● 2026-04-13 00:03:26
● 2026-08-12 23:32:38
●NSns34.domaincontrol.com2026-04-13 → 2026-08-12 · 3 obs
● 2026-04-13 00:03:26
● 2026-08-12 23:32:38
○NSns4.p05.dynect.net2015-08-10 → 2016-09-12 · 5 obs
● 2015-08-10 00:33:04
● 2016-09-12 15:00:54
○ 2016-10-24 13:32:30
○ 2026-08-12 23:32:38
○NSns5.dnsmadeeasy.com2016-11-01 → 2017-08-01 · 5 obs
● 2016-11-01 19:41:40
● 2017-08-01 05:57:52
○ 2026-04-13 00:03:26
○ 2026-08-12 23:32:38
○NSns6.dnsmadeeasy.com2016-11-01 → 2017-08-01 · 5 obs
● 2016-11-01 19:41:40
● 2017-08-01 05:57:52
○ 2026-04-13 00:03:26
○ 2026-08-12 23:32:38
○NSns7.dnsmadeeasy.com2016-11-01 → 2017-08-01 · 5 obs
● 2016-11-01 19:41:40
● 2017-08-01 05:57:52
○ 2026-04-13 00:03:26
○ 2026-08-12 23:32:38
○NSt.ns.verio.net2007-10-22 → 2007-10-22 · 3 obs
○ 2015-08-10 00:33:04
○ 2026-08-12 23:32:38
●MXalt1.aspmx.l.google.com2015-08-10 → 2026-08-12 · 3 obs
● 2015-08-10 00:33:04
● 2026-08-12 23:32:38
●MXalt2.aspmx.l.google.com2015-08-10 → 2026-08-12 · 3 obs
● 2015-08-10 00:33:04
● 2026-08-12 23:32:38
●MXaspmx.l.google.com2015-08-10 → 2026-08-12 · 3 obs
● 2015-08-10 00:33:04
● 2026-08-12 23:32:38
●MXaspmx2.googlemail.com2015-08-10 → 2026-08-12 · 3 obs
● 2015-08-10 00:33:04
● 2026-08-12 23:32:38
●MXaspmx3.googlemail.com2015-08-10 → 2026-08-12 · 3 obs
● 2015-08-10 00:33:04
● 2026-08-12 23:32:38
○MXmailhost.midrid.com2007-10-22 → 2007-10-22 · 3 obs
○ 2015-08-10 00:33:04
○ 2026-08-12 23:32:38
○A204.75.13.792016-11-01 → 2017-08-01 · 5 obs
● 2016-11-01 19:41:40
● 2017-08-01 05:57:52
○ 2026-04-13 00:03:26
○ 2026-08-12 23:32:38
○A204.75.13.862015-08-10 → 2016-10-24 · 5 obs
● 2015-08-10 00:33:04
● 2016-10-24 13:32:30
○ 2016-11-01 19:41:40
○ 2026-08-12 23:32:38
○A38.114.105.682007-10-22 → 2007-10-22 · 3 obs
○ 2015-08-10 00:33:04
○ 2026-08-12 23:32:38
●A72.52.184.752026-04-13 → 2026-08-12 · 3 obs
● 2026-04-13 00:03:26
● 2026-08-12 23:32:38
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| midrid.com | ns33.domaincontrol.com, ns34.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.74.17
NS records: ns33.domaincontrol.com, ns34.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for midrid.com (unsigned zone)
⏱️ Timing
Total: 749ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 72.52.184.75 |
| NS | 2 | ns33.domaincontrol.com, ns34.domaincontrol.com |
| MX | 5 | aspmx.l.google.com (pri: 1), aspmx2.googlemail.com (pri: 10)... |
| TXT | 4 | v=spf1 a include:_spf.google.com include, google-site-verification=aUO1hnpCjjNU3Iu... |
| SOA | 1 | ns33.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns33.domaincontrol.com, ns33.domaincontrol.com, ns34.domaincontrol.com...)
Analysis
Hierarchy
www.midrid.com is a subdomain of midrid.com.
IP Addresses
midrid.com has exactly one IP address — 72.52.184.75.
dialmed.com, freshette.com, cwtile.com plus two other host names have IP numbers in common with midrid.com.
Name Servers
midrid.com uses two name servers for its delegation: ns33.domaincontrol.com and ns34.domaincontrol.com.
The name server configuration of midrid.com is shared with other domains, for instance eifelpark.de, lotienestodo.com, bearstorebr.com and two others.
The two host names ns33.domaincontrol.com and ns34.domaincontrol.com each have a pair of IP addresses: ns33.domaincontrol.com has 97.74.106.17 and 2603:5:21a1::11, and ns34.domaincontrol.com has 173.201.74.17 and 2603:5:22a1::11.
Mail Servers
midrid.com has five mail servers, which are aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
At least some of the mail servers used by midrid.com are shared with other domains: sarithm.com, ns500742.ns500742.ns500742.ns500671.ns500742.ns500671.ns500688.ns500705.ns500705.ns500705.ns500671.ns500671.ns500649.lustychickser.com, ns500671.ns500671.ns500731.ns500742.ns500742.ns500754.ns500705.ns500671.ns500704.ns500678.ns500688.ns500688.ns500671.ns500649.ns500649.lustychickser.com and two others among them.
These mail servers are often deployed together with alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 other mail servers.
Host names pointing to two IP addresses:
aspmx2.googlemail.com directs traffic to 192.178.234.26 and 2800:3f0:4003:c14::1a.
aspmx3.googlemail.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com directs traffic to 172.253.122.26 and 2607:f8b0:4004:c0b::1b.
alt1.aspmx.l.google.com directs traffic to 192.178.234.26 and 2800:3f0:4003:c14::1a.
alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c14::1a IP addresses each.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 192.178.234.26 IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 2a00:1450:400b:c02::1a IP addresses each.