🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`stringscorp.com`

DNSSEC	⚠️ Not signed
A	3.33.130.190^{🇺🇸 Amazon3.33.128.0/20}
		PTR	`a2aa9ff50de748dbe.awsglobalaccelerator.com`
A	15.197.148.33^{🇺🇸 Amazon15.197.144.0/20}
NS	`ns67.domaincontrol.com` ⭐
		A	2603:5:2174::2c^{🇺🇸 GODADDY-DNS2603:5:2170::/44}
			PTR	`ns67.domaincontrol.com`
		A	97.74.103.44^{🇺🇸 GODADDY-DNS97.74.102.0/23}
			PTR	`ns67.domaincontrol.com`
NS	`ns68.domaincontrol.com`
		A	2603:5:2274::2c^{🇺🇸 GODADDY-DNS2603:5:2270::/44}
			PTR	`ns68.domaincontrol.com`
		A	173.201.71.44^{🇺🇸 GODADDY-DNS173.201.70.0/23}
			PTR	`ns68.domaincontrol.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c17::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bl-in-f27.1e100.net`
		A	142.251.16.26^{🇺🇸 Google142.251.16.0/24}
			PTR	`bl-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.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.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`google-site-verification=Tj3uwbUsnDH1HEyoclgQwIqfENMPR2aPbdQKO9EwA3w`
TXT	`v=spf1 include:dc-aa8e722993._spfm.stringscorp.com ~all`
TXT	`google-site-verification=50htX19IV0BmSP29f3j79PNHiWUcEqYLWGRBeyKQoic`
SOA	`ns67.domaincontrol.com`dns@jomax.net 2026-03-05 #1

`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=1791817129

Same first word

stringscorp.com

Similar names

crsportings.com

Previous names

Next names

DNS History

11 records (9 active, 2 former)

●NSns67.domaincontrol.com2016-04-24 → 2026-10-12 · 2 obs

● 2016-04-24 14:45:54
● 2026-10-12 15:29:04

●NSns68.domaincontrol.com2016-04-24 → 2026-10-12 · 2 obs

● 2016-04-24 14:45:54
● 2026-10-12 15:29:04

●MXalt1.aspmx.l.google.com2026-09-10 → 2026-10-12 · 3 obs

○ 2017-07-08 04:42:54
● 2026-09-10 22:37:36
● 2026-10-12 15:29:04

●MXalt2.aspmx.l.google.com2026-09-10 → 2026-10-12 · 3 obs

○ 2017-07-08 04:42:54
● 2026-09-10 22:37:36
● 2026-10-12 15:29:04

●MXalt3.aspmx.l.google.com2026-09-10 → 2026-10-12 · 3 obs

○ 2017-07-08 04:42:54
● 2026-09-10 22:37:36
● 2026-10-12 15:29:04

●MXalt4.aspmx.l.google.com2026-09-10 → 2026-10-12 · 3 obs

○ 2017-07-08 04:42:54
● 2026-09-10 22:37:36
● 2026-10-12 15:29:04

●MXaspmx.l.google.com2026-09-10 → 2026-10-12 · 3 obs

○ 2017-07-08 04:42:54
● 2026-09-10 22:37:36
● 2026-10-12 15:29:04

○MXmail.stringscorp.com2016-04-24 → 2017-07-08 · 4 obs

● 2016-04-24 14:45:54
● 2017-07-08 04:42:54
○ 2026-09-10 22:37:36
○ 2026-10-12 15:29:04

●A15.197.148.332026-09-10 → 2026-10-12 · 3 obs

○ 2017-07-08 04:42:54
● 2026-09-10 22:37:36
● 2026-10-12 15:29:04

○A166.62.28.1142016-04-24 → 2017-07-08 · 4 obs

● 2016-04-24 14:45:54
● 2017-07-08 04:42:54
○ 2026-09-10 22:37:36
○ 2026-10-12 15:29:04

●A3.33.130.1902026-09-10 → 2026-10-12 · 3 obs

○ 2017-07-08 04:42:54
● 2026-09-10 22:37:36
● 2026-10-12 15:29:04

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	d.gtld-servers.net, b.gtld-servers.net, f.gtld-servers.net, h.gtld-servers.net...	-
stringscorp.com	ns67.domaincontrol.com, ns68.domaincontrol.com	4 records

✅ Authoritative Response

Server:97.74.103.44

NS records: ns67.domaincontrol.com, ns68.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for stringscorp.com (unsigned zone)

⏱️ Timing

Total: 1046ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`3.33.130.190, 15.197.148.33`
NS	2	`ns67.domaincontrol.com, ns68.domaincontrol.com`
MX	5	`aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...`
TXT	3	`google-site-verification=Tj3uwbUsnDH1HEy, v=spf1 include:dc-aa8e722993._spfm.strin...`
SOA	1	`ns67.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns67.domaincontrol.com, ns67.domaincontrol.com, ns68.domaincontrol.com...)

Analysis

IP Addresses

stringscorp.com directs to two IP numbers, 3.33.130.190 and 15.197.148.33

tenovalle.com, hillcountryhighpointglampingandrvresort.com, coppercauldron.co.uk plus two other host names have IP numbers in common with stringscorp.com.

Name Servers

stringscorp.com is served by two delegated name servers, ns67.domaincontrol.com and ns68.domaincontrol.com.

The name server configuration of stringscorp.com is shared with other domains, for instance womensbasketballnews.com, ryanrevs.com, non-toi.ca and two others.

Each of the two host names carries two IP addresses: ns67.domaincontrol.com points to 97.74.103.44 and 2603:5:2174::2c, and ns68.domaincontrol.com points to 173.201.71.44 and 2603:5:2274::2c.

Mail Servers

Mail for stringscorp.com is handled by five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

At least some of the mail servers used by stringscorp.com are shared with other domains: sssru.com, pacificblueinc.com, produtoracarat.com.br and two others among them.

These mail servers are often deployed together with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 other mail servers.

Host names pointing to two IP addresses:

aspmx.l.google.com maps to two IP addresses — 142.251.16.26 and 2607:f8b0:4004:c17::1b.

alt1.aspmx.l.google.com maps to two IP addresses — 192.178.234.27 and 2800:3f0:4003:c14::1b.

alt2.aspmx.l.google.com maps to two IP addresses — 172.253.116.26 and 2a00:1450:400b:c02::1b.

alt3.aspmx.l.google.com maps to two IP addresses — 192.178.223.26 and 2a00:1450:4009:c0f::1b.

alt4.aspmx.l.google.com maps to two IP addresses — 172.253.157.27 and 2a00:1450:400c:c23::1b.