overcall.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`overcall.com`

DNSSEC	⚠️ Not signed
A	107.170.76.162^{🇺🇸 DIGITALOCEAN107.170.0.0/17 DigitalOcean}
NS	`ns1.digitalocean.com` ⭐
		A	2606:4700:52::ac40:34d2^{🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.digitalocean.com`
		A	172.64.52.210^{🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.digitalocean.com`
NS	`ns2.digitalocean.com`
		A	2606:4700:5a::ac40:3515^{🇺🇸 Cloudflare2606:4700:5a::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.digitalocean.com`
		A	172.64.53.21^{🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.digitalocean.com`
NS	`ns3.digitalocean.com` ⚠️ Not in parent delegation
		A	2606:4700:52::ac40:31d1^{🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns3.digitalocean.com`
		A	172.64.49.209^{🇺🇸 Cloudflare172.64.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns3.digitalocean.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c21::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`pe-in-f27.1e100.net`
		A	142.251.163.27^{🇺🇸 Google142.251.163.0/24}
			PTR	`wv-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽²⁰⁾
		A	2800:3f0:4003:c14::1b^{🇨🇱 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	`aspmx2.googlemail.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	`aspmx3.googlemail.com`⁽³⁰⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
TXT	`v=spf1 include:spf.mandrillapp.com ?all`
SOA	`ns1.digitalocean.com`hostmaster@overcall.com serial=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=1786968099

WOT: SAFE (74/100)

Same first word

overcall.com

overcall.eu

Similar names

DNS History

9 records (9 active, 0 former)

●NSns1.digitalocean.com2015-06-01 → 2026-08-17 · 2 obs

● 2015-06-01 00:59:06
● 2026-08-17 12:31:16

●NSns2.digitalocean.com2015-06-01 → 2026-08-17 · 2 obs

● 2015-06-01 00:59:06
● 2026-08-17 12:31:16

●NSns3.digitalocean.com2015-06-01 → 2026-08-17 · 2 obs

● 2015-06-01 00:59:06
● 2026-08-17 12:31:16

●MXalt1.aspmx.l.google.com2015-06-01 → 2026-08-17 · 2 obs

● 2015-06-01 00:59:06
● 2026-08-17 12:31:16

●MXalt2.aspmx.l.google.com2015-06-01 → 2026-08-17 · 2 obs

● 2015-06-01 00:59:06
● 2026-08-17 12:31:16

●MXaspmx.l.google.com2015-06-01 → 2026-08-17 · 2 obs

● 2015-06-01 00:59:06
● 2026-08-17 12:31:16

●MXaspmx2.googlemail.com2015-06-01 → 2026-08-17 · 2 obs

● 2015-06-01 00:59:06
● 2026-08-17 12:31:16

●MXaspmx3.googlemail.com2015-06-01 → 2026-08-17 · 2 obs

● 2015-06-01 00:59:06
● 2026-08-17 12:31:16

●A107.170.76.1622015-06-01 → 2026-08-17 · 2 obs

● 2015-06-01 00:59:06
● 2026-08-17 12:31:16

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
overcall.com	ns1.digitalocean.com, ns2.digitalocean.com	2 records

✅ Authoritative Response

Server:172.64.53.21

NS records: ns1.digitalocean.com, ns2.digitalocean.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for overcall.com (unsigned zone)

⏱️ Timing

Total: 227ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`107.170.76.162`
NS	3	`ns1.digitalocean.com, ns3.digitalocean.com...`
MX	5	`alt2.aspmx.l.google.com (pri: 20), alt1.aspmx.l.google.com (pri: 20)...`
TXT	1	`v=spf1 include:spf.mandrillapp.com ?all`
SOA	1	`ns1.digitalocean.com hostmaster.overcall`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.digitalocean.com, ns2.digitalocean.com)

Analysis

IP Addresses

overcall.com resolves to just one IP address, 107.170.76.162.

Name Servers

The authoritative name servers for overcall.com are ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com — three in total.

At least some of overcall.com's name servers are shared with other domains, for example tracygillanproductions.com, faveocloud.com, 105.62.178.in-addr.arpa and two more.

ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com all resolve to exactly two IP numbers apiece: ns1.digitalocean.com → 172.64.52.210 and 2606:4700:52::ac40:34d2; ns2.digitalocean.com → 172.64.53.21 and 2606:4700:5a::ac40:3515; ns3.digitalocean.com → 172.64.49.209 and 2606:4700:52::ac40:31d1.

Mail Servers

overcall.com has five mail servers, which are aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.

There is at least a partial MX overlap between overcall.com and other domains, including ns500742.ns500671.ns500731.ns500671.ns500742.ns500704.ns500678.ns500671.ns500704.ns500678.ns500291.ns500666.tenderladiesbz.com, eventuno.in, ita.k12.tr and two others.

These mail servers tend to appear in combination with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.

Host names that have two IP addresses:

aspmx2.googlemail.com directs traffic to 192.178.234.27 and 2800:3f0:4003:c14::1b.

aspmx3.googlemail.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1b.

aspmx.l.google.com directs traffic to 142.251.163.27 and 2607:f8b0:4004:c21::1b.

alt1.aspmx.l.google.com directs traffic to 192.178.234.26 and 2800:3f0:4003:c14::1b.

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

Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c14::1b IP addresses each.

Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 172.253.116.27 IP addresses each.