globalresolutions.com - robtex.com

globalresolutions.com

DNSSEC⚠️ Not signed
A172.105.4.49🇨🇦 AKAMAI-LINODE-AP172.105.0.0/19 Akamai Technologies
PTRli1958-49.members.linode.com
NSdns101.register.com ⭐
A162.159.24.117Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
NSdns102.register.com
A162.159.25.158Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
MXalt1.aspmx.l.google.com ⭐
A2800:3f0:4003:c0f::1b🇨🇱 Google2800:3f0:4003::/48
A108.177.123.27🇺🇸 Google108.177.123.0/24
PTRlcscld-in-f27.1e100.net
MXalt2.aspmx.l.google.com ⭐
A2a00:1450:400b:c02::1a🇮🇪 Google2a00:1450:400b::/48
PTRdj-in-f26.1e100.net
A172.253.116.26🇺🇸 Google172.253.116.0/24
PTRdj-in-f26.1e100.net
MXalt3.aspmx.l.google.com ⭐
A2a00:1450:4009:c0f::1a🇬🇧 Google2a00:1450:4009::/48
PTRyulhrs-in-f26.1e100.net
A192.178.223.26🇺🇸 Google192.178.223.0/24
PTRyulhrs-in-f26.1e100.net
MXalt4.aspmx.l.google.com ⭐
A2a00:1450:400c:c00::1a🇧🇪 Google2a00:1450:400c::/48
PTRws-in-f26.1e100.net
PTRws-in-x1a.1e100.net
A173.194.76.26🇺🇸 Google173.194.76.0/24
PTRws-in-f26.1e100.net
MXaspmx.l.google.com ⭐
A2607:f8b0:4023:c06::1b🇺🇸 Google2607:f8b0::/32
PTRdz-in-f27.1e100.net
A74.125.137.27🇺🇸 Google74.125.137.0/24
PTRdy-in-f27.1e100.net
TXTgoogle-site-verification=6iX36qO7iT6rPfWXonx_WTGFonFLXHzJPxMvxFqblwM
SOADNS101.REGISTER.comroot@REGISTER.com serial=124032510

com

DNSSEC🔒 Signed (DS record present)
NSa.gtld-servers.net ⭐
NSb.gtld-servers.net
NSc.gtld-servers.net
NSd.gtld-servers.net
NSe.gtld-servers.net
NSf.gtld-servers.net
NSg.gtld-servers.net
NSh.gtld-servers.net
NSi.gtld-servers.net
NSj.gtld-servers.net
NSk.gtld-servers.net
NSl.gtld-servers.net
NSm.gtld-servers.net
SOAa.gtld-servers.netnstld@verisign-grs.com serial=1775984962

Previously MX for

globalresolutions.com

Same first word

globalresolutions.co
globalresolutions.com
globalresolutions.ca

DNS History

15 records (8 active, 7 former)

200920112013201520172019202120232025NSdns101.register.comdns102.register.commap1.sibername.commap2.sibername.comns5.sibername.comns6.sibername.comMXalt1.aspmx.l.google.comalt2.aspmx.l.google.comalt3.aspmx.l.google.comalt4.aspmx.l.google.comaspmx.l.google.comglobalresolutions.comA172.105.4.4964.247.58.24967.212.67.114
●NSdns101.register.com2026-03-26 → 2026-04-12 · 3 obs
○ 2017-06-25 02:03:50
● 2026-03-26 01:21:46
● 2026-04-12 09:12:14
●NSdns102.register.com2026-03-26 → 2026-04-12 · 3 obs
○ 2017-06-25 02:03:50
● 2026-03-26 01:21:46
● 2026-04-12 09:12:14
○NSmap1.sibername.com2015-06-12 → 2017-06-25 · 5 obs
○ 2008-03-20 10:10:40
● 2015-06-12 21:02:18
● 2017-06-25 02:03:50
○ 2026-03-26 01:21:46
○ 2026-04-12 09:12:14
○NSmap2.sibername.com2015-06-12 → 2017-06-25 · 5 obs
○ 2008-03-20 10:10:40
● 2015-06-12 21:02:18
● 2017-06-25 02:03:50
○ 2026-03-26 01:21:46
○ 2026-04-12 09:12:14
○NSns5.sibername.com2008-03-20 → 2008-03-20 · 3 obs
● 2008-03-20 10:10:40
○ 2015-06-12 21:02:18
○ 2026-04-12 09:12:14
○NSns6.sibername.com2008-03-20 → 2008-03-20 · 3 obs
● 2008-03-20 10:10:40
○ 2015-06-12 21:02:18
○ 2026-04-12 09:12:14
●MXalt1.aspmx.l.google.com2016-09-23 → 2026-04-12 · 3 obs
○ 2016-04-07 13:25:28
● 2016-09-23 21:09:06
● 2026-04-12 09:12:14
●MXalt2.aspmx.l.google.com2016-09-23 → 2026-04-12 · 3 obs
○ 2016-04-07 13:25:28
● 2016-09-23 21:09:06
● 2026-04-12 09:12:14
●MXalt3.aspmx.l.google.com2016-09-23 → 2026-04-12 · 3 obs
○ 2016-04-07 13:25:28
● 2016-09-23 21:09:06
● 2026-04-12 09:12:14
●MXalt4.aspmx.l.google.com2016-09-23 → 2026-04-12 · 3 obs
○ 2016-04-07 13:25:28
● 2016-09-23 21:09:06
● 2026-04-12 09:12:14
●MXaspmx.l.google.com2016-09-23 → 2026-04-12 · 3 obs
○ 2016-04-07 13:25:28
● 2016-09-23 21:09:06
● 2026-04-12 09:12:14
○MXglobalresolutions.com2015-06-12 → 2016-04-07 · 5 obs
○ 2008-03-20 10:10:40
● 2015-06-12 21:02:18
● 2016-04-07 13:25:28
○ 2016-09-23 21:09:06
○ 2026-04-12 09:12:14
●A172.105.4.492026-03-26 → 2026-04-12 · 3 obs
○ 2017-06-25 02:03:50
● 2026-03-26 01:21:46
● 2026-04-12 09:12:14
○A64.247.58.2492008-03-20 → 2008-03-20 · 3 obs
● 2008-03-20 10:10:40
○ 2015-06-12 21:02:18
○ 2026-04-12 09:12:14
○A67.212.67.1142015-06-12 → 2017-06-25 · 5 obs
○ 2008-03-20 10:10:40
● 2015-06-12 21:02:18
● 2017-06-25 02:03:50
○ 2026-03-26 01:21:46
○ 2026-04-12 09:12:14

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
globalresolutions.comdns101.register.com, dns102.register.com2 records

✅ Authoritative Response

Server:162.159.25.158

NS records: dns101.register.com, dns102.register.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for globalresolutions.com (unsigned zone)

⏱️ Timing

Total: 245ms | Queries: -

📄 Records

TypeCountSample Data
A1172.105.4.49
NS2dns102.register.com, dns101.register.com
MX5alt1.aspmx.l.google.com (pri: 10), aspmx.l.google.com (pri: 10)...
TXT1google-site-verification=6iX36qO7iT6rPfW
SOA1DNS101.REGISTER.com root.REGISTER.com

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (dns101.register.com, dns102.register.com)

Analysis

IP Addresses

globalresolutions.com points to a single IP number: 172.105.4.49.

Name Servers

globalresolutions.com is delegated to two name servers: dns101.register.com and dns102.register.com.

globalresolutions.com uses the same name server setup as other domains, for instance gsequipmentcanada.com, fighton.com, jukarta.com, yeomar.com and whitehousefinancialgroup.org.

globalresolutions.com partially shares name servers with other domains, for instance zistalk.com.

Host names with one IP number:

dns101.register.com points to: 162.159.24.117.

dns102.register.com points to: 162.159.25.158.

Mail Servers

globalresolutions.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.

globalresolutions.com shares some mail servers with other domains, including ns500759.ns500759.ns500759.ns500759.ns500758.ns500735.ns500736.ns500735.ns500735.ns500708.ns500576.ns500708.ns500652.trackreceptor.com, ns500698.ns500759.ns500698.ns500758.ns500758.ns500736.ns500736.ns500698.ns500708.ns500698.ns500698.ns500576.ns500576.ns500576.ns500619.ns500619.trackreceptor.com, ns500693.ns500693.ns500734.ns500734.ns500693.ns500699.ns500734.ns500693.ns500588.ns500632.ns500632.ns500588.ns500110.dtrkdll.com, ns500765.ns500734.ns500734.ns500734.ns500693.ns500699.ns500588.ns500683.ns500699.ns500683.ns500693.ns500693.ns500602.dtrkdll.com and ns500754.ns500731.ns500742.ns500731.ns500731.ns500731.ns500731.ns500688.ns500291.ns500291.ns500678.ns500291.ns500131.lustychickser.com.

these mail servers are commonly 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:4023:c06::1b and 74.125.137.27.

alt1.aspmx.l.google.com points to 2800:3f0:4003:c0f::1b and 108.177.123.27.

alt2.aspmx.l.google.com points to 2a00:1450:400b:c02::1a and 172.253.116.26.

alt3.aspmx.l.google.com points to 2a00:1450:4009:c0f::1a and 192.178.223.26.

alt4.aspmx.l.google.com points to 2a00:1450:400c:c00::1a and 173.194.76.26.