`sanfercom.com`

DNSSEC	⚠️ Not signed
A	2a02:4780:1:1165:0:124d:11b9:2^{🇺🇸 IIHOS0012a02:4780:1::/48 HOSTINGER US}
A	195.179.239.82^{🇺🇸 IIHOS001195.179.238.0/23 HOSTINGER US}
NS	`ns1.dns-parking.com` ⭐
		A	2400:cb00:2049:1::a29f:18c9^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.24.201^{Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.dns-parking.com`
NS	`ns2.dns-parking.com`
		A	2400:cb00:2049:1::a29f:192a^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.25.42^{Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.dns-parking.com`
MX	`mx1.titan.email` ⭐
		A	3.216.63.151^{🇺🇸 Amazon3.208.0.0/12 EC2 IAD prefix}
			PTR	`ec2-3-216-63-151.compute-1.amazonaws.com`
		A	18.211.45.15^{🇺🇸 Amazon18.208.0.0/13 EC2 IAD prefix}
			PTR	`ec2-18-211-45-15.compute-1.amazonaws.com`
		A	52.5.58.87^{🇺🇸 Amazon52.4.0.0/14 EC2 IAD prefix}
			PTR	`ec2-52-5-58-87.compute-1.amazonaws.com`
MX	`mx2.titan.email`⁽²⁰⁾
		A	3.216.63.151^{🇺🇸 Amazon3.208.0.0/12 EC2 IAD prefix}
			PTR	`ec2-3-216-63-151.compute-1.amazonaws.com`
		A	18.211.45.15^{🇺🇸 Amazon18.208.0.0/13 EC2 IAD prefix}
			PTR	`ec2-18-211-45-15.compute-1.amazonaws.com`
		A	52.5.58.87^{🇺🇸 Amazon52.4.0.0/14 EC2 IAD prefix}
			PTR	`ec2-52-5-58-87.compute-1.amazonaws.com`
TXT	`v=spf1 include:spf.titan.email ~all`
SOA	`ns1.dns-parking.com`dns@hostinger.com 2026-03-19 #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=1774422097

Same first word

sanfercom.com

Similar names

fornesacm.com

cameronfs.com

esmarconf.org

DNS History

16 records (6 active, 10 former)

●NSns1.dns-parking.com2026-02-25 → 2026-03-25 · 3 obs

○ 2019-12-15 08:40:38
● 2026-02-25 20:05:04
● 2026-03-25 07:26:22

○NSns1.hostinger.mx2019-12-15 → 2019-12-15 · 3 obs

● 2019-12-15 08:40:38
○ 2026-02-25 20:05:04
○ 2026-03-25 07:26:22

●NSns2.dns-parking.com2026-02-25 → 2026-03-25 · 3 obs

○ 2019-12-15 08:40:38
● 2026-02-25 20:05:04
● 2026-03-25 07:26:22

○NSns2.hostinger.mx2019-12-15 → 2019-12-15 · 3 obs

● 2019-12-15 08:40:38
○ 2026-02-25 20:05:04
○ 2026-03-25 07:26:22

○NSns3.hostinger.mx2019-12-15 → 2019-12-15 · 3 obs

● 2019-12-15 08:40:38
○ 2026-02-25 20:05:04
○ 2026-03-25 07:26:22

○NSns4.hostinger.mx2019-12-15 → 2019-12-15 · 3 obs

● 2019-12-15 08:40:38
○ 2026-02-25 20:05:04
○ 2026-03-25 07:26:22

○MXmx1.flockmail.com2019-12-15 → 2019-12-15 · 3 obs

● 2019-12-15 08:40:38
○ 2026-02-25 20:05:04
○ 2026-03-25 07:26:22

●MXmx1.titan.email2026-02-25 → 2026-03-25 · 3 obs

○ 2019-12-15 08:40:38
● 2026-02-25 20:05:04
● 2026-03-25 07:26:22

○MXmx2.flockmail.com2019-12-15 → 2019-12-15 · 3 obs

● 2019-12-15 08:40:38
○ 2026-02-25 20:05:04
○ 2026-03-25 07:26:22

●MXmx2.titan.email2026-02-25 → 2026-03-25 · 3 obs

○ 2019-12-15 08:40:38
● 2026-02-25 20:05:04
● 2026-03-25 07:26:22

○A104.24.108.1892019-12-15 → 2019-12-15 · 3 obs

● 2019-12-15 08:40:38
○ 2026-02-25 20:05:04
○ 2026-03-25 07:26:22

○A104.24.109.1892019-12-15 → 2019-12-15 · 3 obs

● 2019-12-15 08:40:38
○ 2026-02-25 20:05:04
○ 2026-03-25 07:26:22

●A195.179.239.822026-02-25 → 2026-03-25 · 3 obs

○ 2019-12-15 08:40:38
● 2026-02-25 20:05:04
● 2026-03-25 07:26:22

○A2606:4700:30::6818:6cbd2019-12-15 → 2019-12-15 · 3 obs

● 2019-12-15 08:40:38
○ 2026-02-25 20:05:04
○ 2026-03-25 07:26:22

○A2606:4700:30::6818:6dbd2019-12-15 → 2019-12-15 · 3 obs

● 2019-12-15 08:40:38
○ 2026-02-25 20:05:04
○ 2026-03-25 07:26:22

●A2a02:4780:1:1165:0:124d:11b9:22026-02-25 → 2026-03-25 · 3 obs

○ 2019-12-15 08:40:38
● 2026-02-25 20:05:04
● 2026-03-25 07:26:22

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
sanfercom.com	ns1.dns-parking.com, ns2.dns-parking.com	4 records

✅ Authoritative Response

Server:162.159.25.42

NS records: ns1.dns-parking.com, ns2.dns-parking.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for sanfercom.com (unsigned zone)

⏱️ Timing

Total: 183ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`195.179.239.82`
AAAA	1	`2a02:4780:1:1165:0:124d:11b9:2`
NS	2	`ns2.dns-parking.com, ns1.dns-parking.com`
MX	2	`mx1.titan.email (pri: 10), mx2.titan.email (pri: 20)`
TXT	1	`v=spf1 include:spf.titan.email ~all`
SOA	1	`ns1.dns-parking.com dns.hostinger.com`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.dns-parking.com, ns1.dns-parking.com, ns2.dns-parking.com...)

Analysis

IP Addresses

sanfercom.com points to two IP numbers: 2a02:4780:1:1165:0:124d:11b9:2 and 195.179.239.82.

Other host names such as wikt.com.br, blogzn.com, velocom.ca, foovler.com and techshop.ca share IP numbers with sanfercom.com.

Name Servers

sanfercom.com is delegated to two name servers: ns1.dns-parking.com and ns2.dns-parking.com.

sanfercom.com uses the same name server setup as other domains, including loudwebmidia.com.br, christmasicerinks.com, bordatec.com, anpuneri.org and okresult.com.

Host names with two IP numbers:

ns1.dns-parking.com points to 2400:cb00:2049:1::a29f:18c9 and 162.159.24.201.

ns2.dns-parking.com points to 2400:cb00:2049:1::a29f:192a and 162.159.25.42.

Mail Servers

sanfercom.com is handled by two mail servers: mx1.titan.email and mx2.titan.email.

sanfercom.com uses the same mail server setup as other domains, for instance akun.com.ar, seatonspeaks.com, khamush.com, kotevski.net and karatt.net.