`sealreliability.com`

DNSSEC	⚠️ Not signed
A	217.19.248.132^{🇬🇧 SAFENAMES-AS217.19.248.0/24 Safenames Datacentre}
		PTR	`redirect.idp365.net`
NS	`dns1.safenames.com` ⭐
		A	2400:cb00:2049:1::a29f:3084^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.48.132^{Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`dns1.safenames.com`
NS	`dns2.safenames.net`
		A	2400:cb00:2049:1::a29f:31aa^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.49.170^{Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`dns2.safenames.net`
NS	`dns3.safenames.org`
		A	2400:cb00:2049:1::ac40:3017^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	172.64.48.23^{🇺🇸 Cloudflare172.64.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`dns3.safenames.org`
MX	`relay1.netnames.net` ⭐
		A	185.26.230.83^{🇬🇧 NETNAMES185.26.230.0/24 NetNames Operations Limited}
			PTR	`relay1.netnames.net`
MX	`relay2.netnames.net`⁽²⁰⁾
		A	185.26.230.89^{🇬🇧 NETNAMES185.26.230.0/24 NetNames Operations Limited}
			PTR	`relay2.netnames.net`
TXT	`_globalsign-domain-verification=L1txfmtGIMSx7fRc0FskFiE3w/nKiGKF91jjc9kCY4s=`
TXT	`v=spf1 include:2248916.spf03.hubspotemail.net –all`
TXT	`v=spf1 include:2248916.spf03.hubspotemail.net -all`
SOA	`dns1.safenames.com`hostmaster@safenames.net 2020-06-18 #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=1776060412

Same first word

sealreliability.com

DNS History

18 records (6 active, 12 former)

○NSdns1.name-services.com2008-03-16 → 2008-03-16 · 3 obs

● 2008-03-16 05:46:16
○ 2015-07-05 14:32:44
○ 2026-04-13 06:33:18

●NSdns1.safenames.com2026-03-29 → 2026-04-13 · 3 obs

○ 2017-04-10 14:14:20
● 2026-03-29 19:41:50
● 2026-04-13 06:33:18

○NSdns2.name-services.com2008-03-16 → 2008-03-16 · 3 obs

● 2008-03-16 05:46:16
○ 2015-07-05 14:32:44
○ 2026-04-13 06:33:18

●NSdns2.safenames.net2026-03-29 → 2026-04-13 · 3 obs

○ 2017-04-10 14:14:20
● 2026-03-29 19:41:50
● 2026-04-13 06:33:18

○NSdns3.name-services.com2008-03-16 → 2008-03-16 · 3 obs

● 2008-03-16 05:46:16
○ 2015-07-05 14:32:44
○ 2026-04-13 06:33:18

●NSdns3.safenames.org2026-03-29 → 2026-04-13 · 3 obs

○ 2017-04-10 14:14:20
● 2026-03-29 19:41:50
● 2026-04-13 06:33:18

○NSdns4.name-services.com2008-03-16 → 2008-03-16 · 3 obs

● 2008-03-16 05:46:16
○ 2015-07-05 14:32:44
○ 2026-04-13 06:33:18

○NSdns5.name-services.com2008-03-16 → 2008-03-16 · 3 obs

● 2008-03-16 05:46:16
○ 2015-07-05 14:32:44
○ 2026-04-13 06:33:18

○NSns1.netnames.net2015-07-05 → 2017-04-10 · 5 obs

○ 2008-03-16 05:46:16
● 2015-07-05 14:32:44
● 2017-04-10 14:14:20
○ 2026-03-29 19:41:50
○ 2026-04-13 06:33:18

○NSns2.netnames.net2015-07-05 → 2017-04-10 · 5 obs

○ 2008-03-16 05:46:16
● 2015-07-05 14:32:44
● 2017-04-10 14:14:20
○ 2026-03-29 19:41:50
○ 2026-04-13 06:33:18

○NSns5.netnames.net2015-07-05 → 2017-04-10 · 5 obs

○ 2008-03-16 05:46:16
● 2015-07-05 14:32:44
● 2017-04-10 14:14:20
○ 2026-03-29 19:41:50
○ 2026-04-13 06:33:18

○NSns6.netnames.net2015-07-05 → 2017-04-10 · 5 obs

○ 2008-03-16 05:46:16
● 2015-07-05 14:32:44
● 2017-04-10 14:14:20
○ 2026-03-29 19:41:50
○ 2026-04-13 06:33:18

●MXrelay1.netnames.net2015-07-05 → 2026-04-13 · 3 obs

○ 2008-03-16 05:46:16
● 2015-07-05 14:32:44
● 2026-04-13 06:33:18

●MXrelay2.netnames.net2015-07-05 → 2026-04-13 · 3 obs

○ 2008-03-16 05:46:16
● 2015-07-05 14:32:44
● 2026-04-13 06:33:18

○A185.26.230.1292016-09-13 → 2017-04-10 · 5 obs

○ 2016-04-10 10:17:38
● 2016-09-13 22:06:36
● 2017-04-10 14:14:20
○ 2026-03-29 19:41:50
○ 2026-04-13 06:33:18

○A212.48.67.1822015-07-05 → 2016-04-10 · 5 obs

○ 2008-03-16 05:46:16
● 2015-07-05 14:32:44
● 2016-04-10 10:17:38
○ 2016-09-13 22:06:36
○ 2026-04-13 06:33:18

●A217.19.248.1322026-03-29 → 2026-04-13 · 3 obs

○ 2017-04-10 14:14:20
● 2026-03-29 19:41:50
● 2026-04-13 06:33:18

○A69.64.155.1432008-03-16 → 2008-03-16 · 3 obs

● 2008-03-16 05:46:16
○ 2015-07-05 14:32:44
○ 2026-04-13 06:33:18

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net...	-
sealreliability.com	dns1.safenames.com, dns2.safenames.net, dns3.safenames.org	2 records

✅ Authoritative Response

Server:162.159.49.170

NS records: dns1.safenames.com, dns2.safenames.net, dns3.safenames.org

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for sealreliability.com (unsigned zone)

⏱️ Timing

Total: 556ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`217.19.248.132`
NS	3	`dns3.safenames.org, dns1.safenames.com...`
MX	2	`relay1.netnames.net (pri: 10), relay2.netnames.net (pri: 20)`
TXT	3	`_globalsign-domain-verification=L1txfmtG, v=spf1 include:2248916.spf03.hubspotemai...`
SOA	1	`dns1.safenames.com hostmaster.safenames.`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (dns1.safenames.com, dns1.safenames.com)

Analysis

IP Addresses

sealreliability.com points to a single IP address: 217.19.248.132.

Other host names such as morefirecrewonline.net, maritimeprotection.net, rohandesigns.info, ernstyoung.lt and www.fpdsavills.com share IP numbers with sealreliability.com.

Name Servers

sealreliability.com is delegated to three name servers: dns1.safenames.com, dns2.safenames.net and dns3.safenames.org.

At least part of the name servers for sealreliability.com are shared with other domains, for instance 241.19.217.in-addr.arpa, dell-technology.org, cushmanwakefield.com.tr, alienware.tech and totetowcester.com.

Host names with two IP numbers:

dns1.safenames.com points to 2400:cb00:2049:1::a29f:3084 and 162.159.48.132

dns2.safenames.net points to 2400:cb00:2049:1::a29f:31aa and 162.159.49.170

dns3.safenames.org points to 2400:cb00:2049:1::ac40:3017 and 172.64.48.23

Mail Servers

sealreliability.com is handled by two mail servers: relay1.netnames.net and relay2.netnames.net.

sealreliability.com uses the same mail server setup as other domains, for instance xn--80aaa7bse.xn--p1ai, onlinebanking.iombank.com, unionstrongdc5.com, framatch.net and networkappliance.com.es.

sealreliability.com shares some mail servers with other domains at least partially, for example berendsen.international, assaycentral.com and angardstaffing.com.

Hostnames with a single IP

relay1.netnames.net resolves to: 185.26.230.83.

relay2.netnames.net resolves to: 185.26.230.89.

sealreliability.com - robtex.com