🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`opsframework.com`

DNSSEC	⚠️ Not signed
A	162.159.140.166^{Cloudflare162.159.128.0/19 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns33.domaincontrol.com` ⭐
		A	2603:5:21a1::11^{🇺🇸 GODADDY-DNS2603:5:21a0::/44}
			PTR	`ns33.domaincontrol.com`
		A	97.74.106.17^{🇺🇸 GODADDY-DNS97.74.106.0/23}
			PTR	`ns33.domaincontrol.com`
NS	`ns34.domaincontrol.com`
		A	2603:5:22a1::11^{🇺🇸 GODADDY-DNS2603:5:22a0::/44}
			PTR	`ns34.domaincontrol.com`
		A	173.201.74.17^{🇺🇸 GODADDY-DNS173.201.74.0/23}
			PTR	`ns34.domaincontrol.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c21::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`pe-in-f26.1e100.net`
		A	172.253.63.26^{🇺🇸 Google172.253.63.0/24}
			PTR	`bi-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::1a^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f26.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::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f26.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`google-site-verification=F8JTbp2l6X6z0PH292UGUidpKy6CHv1zQTYmrbMCRHI`
TXT	`brevo-code:8d4b9d04adcfbe113a9d2503e5ddc21a`
TXT	`v=spf1 include:_spf.google.com ~all`
SOA	`ns33.domaincontrol.com`dns@jomax.net 2026-09-23 #17

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

Same first word

opsframework.com

opsframework.org

opsframework.co.uk

Similar names

frameworkops.xyz

posframework.com

sopframework.com

Previous names

Next names

DNS History

12 records (8 active, 4 former)

●NSns33.domaincontrol.com2026-08-31 → 2026-10-08 · 3 obs

○ 2017-10-03 15:57:26
● 2026-08-31 09:45:36
● 2026-10-08 23:19:14

●NSns34.domaincontrol.com2026-08-31 → 2026-10-08 · 3 obs

○ 2017-10-03 15:57:26
● 2026-08-31 09:45:36
● 2026-10-08 23:19:14

○NSns8175.hostgator.com2016-12-19 → 2017-10-03 · 4 obs

● 2016-12-19 08:18:38
● 2017-10-03 15:57:26
○ 2026-08-31 09:45:36
○ 2026-10-08 23:19:14

○NSns8176.hostgator.com2016-12-19 → 2017-10-03 · 4 obs

● 2016-12-19 08:18:38
● 2017-10-03 15:57:26
○ 2026-08-31 09:45:36
○ 2026-10-08 23:19:14

●MXalt1.aspmx.l.google.com2026-08-31 → 2026-10-08 · 3 obs

○ 2017-10-03 15:57:26
● 2026-08-31 09:45:36
● 2026-10-08 23:19:14

●MXalt2.aspmx.l.google.com2026-08-31 → 2026-10-08 · 3 obs

○ 2017-10-03 15:57:26
● 2026-08-31 09:45:36
● 2026-10-08 23:19:14

●MXalt3.aspmx.l.google.com2026-08-31 → 2026-10-08 · 3 obs

○ 2017-10-03 15:57:26
● 2026-08-31 09:45:36
● 2026-10-08 23:19:14

●MXalt4.aspmx.l.google.com2026-08-31 → 2026-10-08 · 3 obs

○ 2017-10-03 15:57:26
● 2026-08-31 09:45:36
● 2026-10-08 23:19:14

●MXaspmx.l.google.com2026-08-31 → 2026-10-08 · 3 obs

○ 2017-10-03 15:57:26
● 2026-08-31 09:45:36
● 2026-10-08 23:19:14

○MXmail.opsframework.com2016-12-19 → 2017-10-03 · 4 obs

● 2016-12-19 08:18:38
● 2017-10-03 15:57:26
○ 2026-08-31 09:45:36
○ 2026-10-08 23:19:14

●A162.159.140.1662026-08-31 → 2026-10-08 · 3 obs

○ 2017-10-03 15:57:26
● 2026-08-31 09:45:36
● 2026-10-08 23:19:14

○A192.185.35.752016-12-19 → 2017-10-03 · 4 obs

● 2016-12-19 08:18:38
● 2017-10-03 15:57:26
○ 2026-08-31 09:45:36
○ 2026-10-08 23:19:14

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
opsframework.com	ns33.domaincontrol.com, ns34.domaincontrol.com	4 records

✅ Authoritative Response

Server:173.201.74.17

NS records: ns33.domaincontrol.com, ns34.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for opsframework.com (unsigned zone)

⏱️ Timing

Total: 302ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`162.159.140.166`
NS	2	`ns34.domaincontrol.com, ns33.domaincontrol.com`
MX	5	`aspmx.l.google.com (pri: 10), alt2.aspmx.l.google.com (pri: 30)...`
TXT	3	`google-site-verification=F8JTbp2l6X6z0PH, brevo-code:8d4b9d04adcfbe113a9d2503e5ddc...`
SOA	1	`ns33.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns33.domaincontrol.com, ns33.domaincontrol.com, ns34.domaincontrol.com...)

Analysis

IP Addresses

opsframework.com has exactly one IP address — 162.159.140.166.

dutchmelt.com, phronesis-advisory.com, agentraai.com.au plus two other host names have IP numbers in common with opsframework.com.

Name Servers

opsframework.com is delegated to two name servers: ns33.domaincontrol.com and ns34.domaincontrol.com.

The name server configuration of opsframework.com is shared with other domains, for instance rovdrone.com, endoflifeplans.ca, definitelydifferentboutique.com and two others.

opsframework.com shares at least some of its name servers with other domains, such as bodiemorgan.com.

ns33.domaincontrol.com and ns34.domaincontrol.com each resolve to two IP addresses: ns33.domaincontrol.com points to 97.74.106.17 and 2603:5:21a1::11, while ns34.domaincontrol.com points to 173.201.74.17 and 2603:5:22a1::11.

Mail Servers

Mail for opsframework.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 opsframework.com are shared with other domains: kanis.hk, tncpro.com, armetco.com and two others among them.

These mail servers often appear in conjunction with the mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com.

Host names pointing to two IP addresses:

aspmx.l.google.com points to 172.253.63.26 and 2607:f8b0:4004:c21::1a.

alt1.aspmx.l.google.com points to 192.178.234.26 and 2800:3f0:4003:c14::1a.

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

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

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