🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`urcontext.com`

DNSSEC	⚠️ Not signed
A	216.150.1.1^{🇨🇦 Amazon216.150.1.0/24 EC2 Prefix}
NS	`ns03.domaincontrol.com` ⭐
		A	2603:5:2150::2^{🇺🇸 GODADDY-DNS2603:5:2150::/44}
			PTR	`ns03.domaincontrol.com`
		A	97.74.101.2^{🇺🇸 GODADDY-DNS97.74.100.0/23}
			PTR	`ns03.domaincontrol.com`
NS	`ns04.domaincontrol.com`
		A	2603:5:2250::2^{🇺🇸 GODADDY-DNS2603:5:2250::/44}
			PTR	`ns04.domaincontrol.com`
		A	173.201.69.2^{🇺🇸 GODADDY-DNS173.201.68.0/23}
			PTR	`ns04.domaincontrol.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c0b::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bj-in-f27.1e100.net`
		A	64.233.180.26^{🇺🇸 Google64.233.180.0/24}
			PTR	`on-in-f26.1e100.net`
			PTR	`pe-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.26^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.1e100.net`
		A	192.178.223.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1b^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f27.1e100.net`
		A	172.253.157.26^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f26.1e100.net`
TXT	`google-site-verification=lq_vlxZuvSsRvAgcW-6jSdmX6_ZjGErWS5CpwB4_uzc`
TXT	`v=spf1 include:dc-aa8e722993._spfm.urcontext.com ~all`
SOA	`ns03.domaincontrol.com`dns@jomax.net 2026-04-01 #9

`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.net`nstld@verisign-grs.com serial=1787439114

Same first word

urcontext.com

Similar names

contextur.com

courtnext.com

contxture.com

unxttorec.com

nextcourt.com

Previous names

Next names

DNS History

13 records (8 active, 5 former)

●NSns03.domaincontrol.com2026-08-18 → 2026-08-22 · 3 obs

○ 2017-08-14 02:11:42
● 2026-08-18 10:22:04
● 2026-08-22 23:09:22

●NSns04.domaincontrol.com2026-08-18 → 2026-08-22 · 3 obs

○ 2017-08-14 02:11:42
● 2026-08-18 10:22:04
● 2026-08-22 23:09:22

○NSns1.dominioabsoluto.com2017-08-14 → 2017-08-14 · 3 obs

● 2017-08-14 02:11:42
○ 2026-08-18 10:22:04
○ 2026-08-22 23:09:22

○NSns2.dominioabsoluto.com2017-08-14 → 2017-08-14 · 3 obs

● 2017-08-14 02:11:42
○ 2026-08-18 10:22:04
○ 2026-08-22 23:09:22

●MXalt1.aspmx.l.google.com2026-08-18 → 2026-08-22 · 3 obs

○ 2017-08-14 02:11:42
● 2026-08-18 10:22:04
● 2026-08-22 23:09:22

●MXalt2.aspmx.l.google.com2026-08-18 → 2026-08-22 · 3 obs

○ 2017-08-14 02:11:42
● 2026-08-18 10:22:04
● 2026-08-22 23:09:22

●MXalt3.aspmx.l.google.com2026-08-18 → 2026-08-22 · 3 obs

○ 2017-08-14 02:11:42
● 2026-08-18 10:22:04
● 2026-08-22 23:09:22

●MXalt4.aspmx.l.google.com2026-08-18 → 2026-08-22 · 3 obs

○ 2017-08-14 02:11:42
● 2026-08-18 10:22:04
● 2026-08-22 23:09:22

●MXaspmx.l.google.com2026-08-18 → 2026-08-22 · 3 obs

○ 2017-08-14 02:11:42
● 2026-08-18 10:22:04
● 2026-08-22 23:09:22

○MXmx.urcontext.com2017-08-14 → 2017-08-14 · 3 obs

● 2017-08-14 02:11:42
○ 2026-08-18 10:22:04
○ 2026-08-22 23:09:22

●A216.150.1.12026-08-18 → 2026-08-22 · 3 obs

○ 2017-08-14 02:11:42
● 2026-08-18 10:22:04
● 2026-08-22 23:09:22

○A217.116.0.1442017-08-14 → 2017-08-14 · 3 obs

● 2017-08-14 02:11:42
○ 2026-08-18 10:22:04
○ 2026-08-22 23:09:22

○A217.116.0.1912017-08-14 → 2017-08-14 · 3 obs

● 2017-08-14 02:11:42
○ 2026-08-18 10:22:04
○ 2026-08-22 23:09:22

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
urcontext.com	ns03.domaincontrol.com, ns04.domaincontrol.com	4 records

✅ Authoritative Response

Server:97.74.101.2

NS records: ns03.domaincontrol.com, ns04.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for urcontext.com (unsigned zone)

⏱️ Timing

Total: 193ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`216.150.1.1`
NS	2	`ns03.domaincontrol.com, ns04.domaincontrol.com`
MX	5	`aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...`
TXT	2	`google-site-verification=lq_vlxZuvSsRvAg, v=spf1 include:dc-aa8e722993._spfm.urcon`
SOA	1	`ns03.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns03.domaincontrol.com, ns03.domaincontrol.com, ns04.domaincontrol.com...)

Analysis

IP Addresses

urcontext.com resolves to just one IP address, 216.150.1.1.

Two other host names, along with tbr.dental, presidentialthcmichigan.com and parscape.com, also share IP numbers with urcontext.com.

Name Servers

urcontext.com uses two name servers for its delegation: ns03.domaincontrol.com and ns04.domaincontrol.com.

urcontext.com shares its NS records with other domains, for example ibox.plus, rfgates.net, leviwa.de and two others.

The two host names ns03.domaincontrol.com and ns04.domaincontrol.com each have a pair of IP addresses: ns03.domaincontrol.com has 97.74.101.2 and 2603:5:2150::2, and ns04.domaincontrol.com has 173.201.69.2 and 2603:5:2250::2.

Mail Servers

urcontext.com has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

There is at least a partial MX overlap between urcontext.com and other domains, including transfernow.fr, tharukirana.com, rodabramsfh.wpengine.com and two others.

These mail servers tend to appear in combination with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.

Host names that have two IP addresses:

aspmx.l.google.com directs traffic to 64.233.180.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.27 and 2a00:1450:400b:c02::1a.

alt3.aspmx.l.google.com directs traffic to 192.178.223.26 and 2a00:1450:4009:c0f::1b.

alt4.aspmx.l.google.com directs traffic to 172.253.157.26 and 2a00:1450:400c:c23::1b.