threecords.com - dns.ninja

`threecords.com`

DNSSEC	⚠️ Not signed
A	13.248.243.5^{🇺🇸 Amazon13.248.240.0/20}
		PTR	`a16e665f42988324c.awsglobalaccelerator.com`
A	76.223.105.230^{🇺🇸 Amazon76.223.96.0/20}
NS	`ns27.domaincontrol.com` ⭐
		A	2603:5:2171::e^{🇺🇸 GODADDY-DNS2603:5:2170::/44}
			PTR	`ns27.domaincontrol.com`
		A	97.74.103.14^{🇺🇸 GODADDY-DNS97.74.102.0/23}
			PTR	`ns27.domaincontrol.com`
NS	`ns28.domaincontrol.com`
		A	2603:5:2271::e^{🇺🇸 GODADDY-DNS2603:5:2270::/44}
			PTR	`ns28.domaincontrol.com`
		A	173.201.71.14^{🇺🇸 GODADDY-DNS173.201.70.0/23}
			PTR	`ns28.domaincontrol.com`
MX	`smtp.google.com` ⭐
		A	2607:f8b0:4004:c09::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bh-in-f27.1e100.net`
		A	2607:f8b0:4004:c23::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadrs-in-f26.1e100.net`
		A	2607:f8b0:4004:c23::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadrs-in-f27.1e100.net`
		A	2607:f8b0:4004:c27::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadsk-in-f26.1e100.net`
		A	172.253.122.26^{🇺🇸 Google172.253.122.0/24}
			PTR	`bh-in-f26.1e100.net`
		A	172.253.122.27^{🇺🇸 Google172.253.122.0/24}
			PTR	`bh-in-f27.1e100.net`
		A	172.253.139.26^{🇺🇸 Google172.253.139.0/24}
			PTR	`yuiadsk-in-f26.1e100.net`
		A	192.178.155.26^{🇺🇸 Google192.178.155.0/24}
			PTR	`yuiadrs-in-f26.1e100.net`
		A	192.178.155.27^{🇺🇸 Google192.178.155.0/24}
			PTR	`yuiadrs-in-f27.1e100.net`
MX	`oqge2khmjfjyxt2e6nxledtnx4fsruxxrcpnbb4occrcb2kbofsq.mx-verification.google.com`⁽¹⁵⁾
SOA	`ns27.domaincontrol.com`dns@jomax.net 2025-05-12 #0

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

WOT: SAFE (3/100)

Same first word

threecords.myshopify.com

threecords.com

threecords.org

Similar names

DNS History

13 records (6 active, 7 former)

○NSns1.smtmdns.com2015-05-10 → 2017-06-11 · 6 obs

● 2015-05-10 12:27:28
○ 2015-10-25 11:45:48
● 2016-01-04 09:51:02
● 2017-06-11 11:59:02
○ 2026-03-03 09:56:34
○ 2026-07-30 17:59:36

○NSns1.threecords.com2015-10-25 → 2015-10-25 · 4 obs

○ 2015-05-10 12:27:28
● 2015-10-25 11:45:48
○ 2016-01-04 09:51:02
○ 2026-07-30 17:59:36

○NSns2.smtmdns.com2015-05-10 → 2017-06-11 · 6 obs

● 2015-05-10 12:27:28
○ 2015-10-25 11:45:48
● 2016-01-04 09:51:02
● 2017-06-11 11:59:02
○ 2026-03-03 09:56:34
○ 2026-07-30 17:59:36

●NSns27.domaincontrol.com2026-03-03 → 2026-07-30 · 3 obs

○ 2017-06-11 11:59:02
● 2026-03-03 09:56:34
● 2026-07-30 17:59:36

●NSns28.domaincontrol.com2026-03-03 → 2026-07-30 · 3 obs

○ 2017-06-11 11:59:02
● 2026-03-03 09:56:34
● 2026-07-30 17:59:36

●MXoqge2khmjfjyxt2e6nxledtnx4fsruxxrcpnbb4occrcb2kbofsq.mx-verification.google.com2026-03-03 → 2026-07-30 · 2 obs

● 2026-03-03 09:56:34
● 2026-07-30 17:59:36

●MXsmtp.google.com2026-03-03 → 2026-07-30 · 2 obs

● 2026-03-03 09:56:34
● 2026-07-30 17:59:36

●A13.248.243.52026-03-03 → 2026-07-30 · 3 obs

○ 2017-06-11 11:59:02
● 2026-03-03 09:56:34
● 2026-07-30 17:59:36

○A216.157.88.242017-06-11 → 2017-06-11 · 4 obs

○ 2016-09-27 04:17:34
● 2017-06-11 11:59:02
○ 2026-03-03 09:56:34
○ 2026-07-30 17:59:36

○A66.135.47.1252015-05-10 → 2015-05-10 · 3 obs

● 2015-05-10 12:27:28
○ 2017-06-11 11:59:02
○ 2026-07-30 17:59:36

●A76.223.105.2302026-03-03 → 2026-07-30 · 3 obs

○ 2017-06-11 11:59:02
● 2026-03-03 09:56:34
● 2026-07-30 17:59:36

○A85.17.25.2142016-09-27 → 2017-06-11 · 5 obs

○ 2016-04-15 08:56:20
● 2016-09-27 04:17:34
● 2017-06-11 11:59:02
○ 2026-03-03 09:56:34
○ 2026-07-30 17:59:36

○A85.17.25.2422015-05-10 → 2016-04-15 · 4 obs

● 2015-05-10 12:27:28
● 2016-04-15 08:56:20
○ 2016-09-27 04:17:34
○ 2026-07-30 17:59:36

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	j.gtld-servers.net, d.gtld-servers.net, c.gtld-servers.net, b.gtld-servers.net...	-
threecords.com	ns27.domaincontrol.com, ns28.domaincontrol.com	4 records

✅ Authoritative Response

Server:97.74.103.14

NS records: ns27.domaincontrol.com, ns28.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for threecords.com (unsigned zone)

⏱️ Timing

Total: 217ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`76.223.105.230, 13.248.243.5`
NS	2	`ns27.domaincontrol.com, ns28.domaincontrol.com`
MX	2	`oqge2khmjfjyxt2e6nxledtnx4fsruxxrcpnbb4o, smtp.google.com (pri: 1)`
SOA	1	`ns27.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns27.domaincontrol.com, ns27.domaincontrol.com, ns28.domaincontrol.com...)

Analysis

IP Addresses

threecords.com points to the IP addresses 13.248.243.5 and 76.223.105.230

Two other host names, along with alphabase.org, foreclosureprofessor.com and letsreadtoday.com, also share IP numbers with threecords.com.

Name Servers

threecords.com has two authoritative name servers — ns27.domaincontrol.com and ns28.domaincontrol.com.

threecords.com shares its NS records with other domains, for example igothay.com, 247-locksmith-dayton.com, burgunderhof.eu and two others.

Both ns27.domaincontrol.com and ns28.domaincontrol.com have two IP addresses each. ns27.domaincontrol.com resolves to 97.74.103.14 and 2603:5:2171::e; ns28.domaincontrol.com resolves to 173.201.71.14 and 2603:5:2271::e.

Mail Servers

threecords.com is served by two mail servers, smtp.google.com and oqge2khmjfjyxt2e6nxledtnx4fsruxxrcpnbb4occrcb2kbofsq.mx-verification.google.com.

There is at least a partial MX overlap between threecords.com and other domains, including e-tedarikci.com, levoilierblanc.com, mwbr.com.br and two others.

These mail servers frequently co-occur with the mail servers aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

DNS names with 9 IP addresses:

smtp.google.com points to 172.253.122.26, 172.253.122.27, 172.253.139.26 and 6 other IP addresses.