ma2.com checked at 2025-02-04T07:29:21.013Z 167ms 100/100/100 100% R:14DNSTREE.COM - ma2.com
Search for IP or hostnames
ma2.com
| NS | ns3.1ruf.com | ||||||
| A | 67.225.188.33🇺🇸 Liquid Web | ||||||
| PTR | email.1ruf.com | ||||||
| NS | ns4.1ruf.com | ||||||
| A | 67.225.188.33🇺🇸 Liquid Web | ||||||
| PTR | email.1ruf.com | ||||||
| MX | aspmx.l.google.com | ||||||
| A | 2a00:1450:400c:c00::1b 🇧🇪 Google | ||||||
| PTR | ws-in-f27.1e100.net | ||||||
| PTR | ws-in-x1b.1e100.net | ||||||
| A | 74.125.71.26🇺🇸 Google | ||||||
| PTR | wn-in-f26.1e100.net | ||||||
| MX | alt1.aspmx.l.google.com | ||||||
| A | 2a00:1450:4013:c16::1b 🇳🇱 Google | ||||||
| PTR | ea-in-f27.1e100.net | ||||||
| A | 142.250.153.26🇺🇸 Google | ||||||
| PTR | ea-in-f26.1e100.net | ||||||
| MX | alt3.aspmx.l.google.com | ||||||
| A | 2a00:1450:4010:c1c::1a 🇫🇮 Google | ||||||
| PTR | la-in-f26.1e100.net | ||||||
| A | 142.250.150.27🇺🇸 Google | ||||||
| PTR | la-in-f27.1e100.net | ||||||
| MX | alt4.aspmx.l.google.com | ||||||
| A | 2404:6800:4003:c00::1a 🇸🇬 Google | ||||||
| PTR | sa-in-f26.1e100.net | ||||||
| PTR | sa-in-x1a.1e100.net | ||||||
| A | 74.125.200.26🇺🇸 Google | ||||||
| PTR | sa-in-f26.1e100.net | ||||||
| A | 209.87.149.148🇺🇸 Nexcess.net LLC | ||||||
| PTR | cloudhost-3090806.us-midwest-1.nxcli.net | ||||||
com
AI analysis
209.87.149.148 is the IP number that ma2.com points to.
IP numbers are shared between ma2.com and other host names such as marwick.ca, cloudhost-3090806.us-midwest-1.nxcli.net, quantumventures.com, servicecpa.com, and azulle.com.
Two name servers, ns3.1ruf.com and ns4.1ruf.com, have been delegated for ma2.com.
The name server setup for ma2.com is shared with other domains, such as iphotosafari.com.
ns3.1ruf.com and ns4.1ruf.com both point to the same IP number: 67.225.188.33.
Four mail servers, aspmx.l.google.com, alt1.aspmx.l.google.com, alt3.aspmx.l.google.com, and alt4.aspmx.l.google.com, manage ma2.com.
Just like domains such as synw.org, reis.me, eeeofamerica.com, jps.om, and fadecloud.com, ma2.com also shares the same mail server setup.
Domains such as ns500671.ns500742.ns500754.ns500742.ns500754.ns500742.ns500705.ns500688.ns500704.ns500688.ns500291.ns500666.ns500291.ns500131.lustychickser.com, ns500693.ns500699.ns500699.ns500699.ns500588.ns500693.ns500693.ns500588.ns500578.ns500110.dtrkdll.com, ns500731.ns500731.ns500754.ns500731.ns500704.ns500704.ns500705.ns500688.ns500678.ns500291.ns500291.ns500131.lustychickser.com, ns500742.ns500671.ns500754.ns500731.ns500731.ns500704.ns500704.ns500704.ns500671.ns500688.ns500671.lustyslutz.com, and ns500698.ns500698.ns500758.ns500698.ns500698.ns500735.ns500736.ns500576.ns500576.ns500708.ns500698.ns500619.ns500686.ns500619.ns500619.trackreceptor.com share some mail servers, at least partially, with ma2.com.
The mail servers alt2.aspmx.l.google.com are commonly utilized in conjunction with these mail servers.
Two IP numbers, 2a00:1450:400c:c00::1b and 74.125.71.26, are pointed to by aspmx.l.google.com. Similarly, alt1.aspmx.l.google.com directs to 2a00:1450:4013:c16::1b and 142.250.153.26. Moreover, alt3.aspmx.l.google.com is associated with 2a00:1450:4010:c1c::1a and 142.250.150.27, and alt4.aspmx.l.google.com points to 2404:6800:4003:c00::1a and 74.125.200.26.
dbq