md-infrastructure.com - robtex.com
md-infrastructure.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=1774744977 | ||||||
Same first word
md-infrastructure.com |
DNS History
15 records (11 active, 4 former)
●NSconnect1.squarespacedns.com2026-02-20 → 2026-03-29 · 2 obs
● 2026-03-29 01:00:58
●NSconnect2.squarespacedns.com2026-02-20 → 2026-03-29 · 2 obs
● 2026-03-29 01:00:58
○NSdns1.p07.nsone.net2026-02-20 → 2026-02-20 · 3 obs
○ 2026-03-29 01:00:56
○ 2026-03-29 01:00:58
○NSdns2.p07.nsone.net2026-02-20 → 2026-02-20 · 3 obs
○ 2026-03-29 01:00:56
○ 2026-03-29 01:00:58
○NSdns3.p07.nsone.net2026-02-20 → 2026-02-20 · 3 obs
○ 2026-03-29 01:00:56
○ 2026-03-29 01:00:58
○NSdns4.p07.nsone.net2026-02-20 → 2026-02-20 · 3 obs
○ 2026-03-29 01:00:56
○ 2026-03-29 01:00:58
●MXalt1.aspmx.l.google.com2026-03-29 → 2026-03-29 · 2 obs
● 2026-03-29 01:00:58
●MXalt2.aspmx.l.google.com2026-03-29 → 2026-03-29 · 2 obs
● 2026-03-29 01:00:58
●MXalt3.aspmx.l.google.com2026-03-29 → 2026-03-29 · 2 obs
● 2026-03-29 01:00:58
●MXalt4.aspmx.l.google.com2026-03-29 → 2026-03-29 · 2 obs
● 2026-03-29 01:00:58
●MXaspmx.l.google.com2026-03-29 → 2026-03-29 · 2 obs
● 2026-03-29 01:00:58
●A198.185.159.1442026-03-29 → 2026-03-29 · 2 obs
● 2026-03-29 01:00:58
●A198.185.159.1452026-03-29 → 2026-03-29 · 2 obs
● 2026-03-29 01:00:58
●A198.49.23.1442026-03-29 → 2026-03-29 · 2 obs
● 2026-03-29 01:00:58
●A198.49.23.1452026-03-29 → 2026-03-29 · 2 obs
● 2026-03-29 01:00:58
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | f.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net, b.gtld-servers.net... | - |
| md-infrastructure.com | connect1.squarespacedns.com, connect2.squarespacedns.com | 2 records |
✅ Authoritative Response
Server:45.54.22.65
NS records: connect1.squarespacedns.com, connect2.squarespacedns.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for md-infrastructure.com (unsigned zone)
⏱️ Timing
Total: 141ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (connect1.squarespacedns.com, connect2.squarespacedns.com)
Analysis
IP Addresses
Four IP numbers are pointed to by md-infrastructure.com: 198.49.23.144, 198.49.23.145, 198.185.159.144 and 198.185.159.145.
other host names including kaminotech.nyc, ohsipp.org, mancelona.org, myphotocurator.com and personalinjuryattorneyguide.com share IP numbers with md-infrastructure.com.
Name Servers
md-infrastructure.com is delegated to two name servers connect1.squarespacedns.com and connect2.squarespacedns.com.
md-infrastructure.com shares the same name server setup as other domains, for instance freshnlaundry.com, lancastech.com, grow-food.com, mx100.org and hcaacd.com.
md-infrastructure.com at least partially shares name servers with other domains, for instance rivieradmc.com, elkinsart.com, barkandbrew.com, highlandsupportproject.org and islandiae.com.
These name servers are commonly used with the following name servers: dns1.p01.nsone.net, ns01.squarespacedns.com, ns02.squarespacedns.com, ns03.squarespacedns.com, ns04.squarespacedns.com, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net, dns1.p05.nsone.net and dns2.p05.nsone.net.
Host names with one IP number:
connect1.squarespacedns.com points to 198.51.45.6
connect2.squarespacedns.com points to 45.54.22.65
Mail Servers
md-infrastructure.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com.
md-infrastructure.com shares some mail servers with other domains, at least partially, for instance ns500758.ns500759.ns500759.ns500735.ns500698.ns500736.ns500698.ns500708.ns500698.ns500619.ns500698.ns500576.ns500619.ns500576.trackreceptor.com, ns500794.ns500841.ns500794.ns500841.ns500841.ns500795.ns500794.ns500795.ns500794.ns500794.ns500795.lustypartnersfinder.com, ns500731.ns500742.ns500742.ns500731.ns500731.ns500731.ns500705.ns500688.ns500705.ns500678.ns500649.ns500688.ns500649.ns500649.lustychickser.com, ns500671.ns500742.ns500742.ns500731.ns500731.ns500671.ns500671.ns500754.ns500731.ns500704.ns500671.ns500688.ns500671.ns500649.ns500649.ns500291.ns500131.lustychickser.com and ns500699.ns500699.ns500734.ns500693.ns500693.ns500699.ns500734.ns500699.ns500693.ns500612.ns500588.ns500612.ns500110.dtrkdll.com.
these mail servers are often used with aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com and aspmx5.googlemail.com.
Host names with two IP numbers:
aspmx.l.google.com points to 2607:f8b0:4004:c23::1b and 172.253.63.26
alt1.aspmx.l.google.com points to 2607:f8b0:4023:2801::1b and 192.178.128.27
alt2.aspmx.l.google.com points to 2607:f8b0:4023:1015::1a and 172.253.135.27
alt3.aspmx.l.google.com points to 2a00:1450:4009:c0f::1a and 192.178.223.26
alt4.aspmx.l.google.com points to 2607:f8b0:4003:c4a::1a and 142.251.96.27