getblocking.com - dns.ninja

`getblocking.com`

DNSSEC	⚠️ Not signed
A	18.196.70.141^{🇩🇪 Amazon18.196.0.0/15 EC2 FRA prefix}
		PTR	`ec2-18-196-70-141.eu-central-1.compute.amazonaws.com`
NS	`ns53.domaincontrol.com` ⭐
		A	2603:5:21a2::1b^{🇺🇸 GODADDY-DNS2603:5:21a0::/44}
			PTR	`ns53.domaincontrol.com`
		A	97.74.106.27^{🇺🇸 GODADDY-DNS97.74.106.0/23}
			PTR	`ns53.domaincontrol.com`
NS	`ns54.domaincontrol.com`
		A	2603:5:22a2::1b^{🇺🇸 GODADDY-DNS2603:5:22a0::/44}
			PTR	`ns54.domaincontrol.com`
		A	173.201.74.27^{🇺🇸 GODADDY-DNS173.201.74.0/23}
			PTR	`ns54.domaincontrol.com`
MX	`mail.innade.cloud` ⭐
		A	167.71.39.1^{🇩🇪 DIGITALOCEAN167.71.32.0/20 DigitalOcean}
			PTR	`mail.innade.cloud`
TXT	`v=spf1 mx ~all`
TXT	`google-site-verification=MJVkqr7w4QH38gSTviCTRPb0x2qqjtylHBTtbuNYsAo`
SOA	`ns53.domaincontrol.com`dns@jomax.net 2022-05-18 #2

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

Same first word

getblocking.com

DNS History

5 records (4 active, 1 former)

●NSns53.domaincontrol.com2019-12-17 → 2026-08-10 · 2 obs

● 2019-12-17 07:22:46
● 2026-08-10 02:57:50

●NSns54.domaincontrol.com2019-12-17 → 2026-08-10 · 2 obs

● 2019-12-17 07:22:46
● 2026-08-10 02:57:50

●MXmail.innade.cloud2026-04-01 → 2026-08-10 · 2 obs

● 2026-04-01 02:53:06
● 2026-08-10 02:57:50

●A18.196.70.1412026-04-01 → 2026-08-10 · 3 obs

○ 2019-12-17 07:22:46
● 2026-04-01 02:53:06
● 2026-08-10 02:57:50

○A3.120.141.802019-12-17 → 2019-12-17 · 3 obs

● 2019-12-17 07:22:46
○ 2026-04-01 02:53:06
○ 2026-08-10 02:57:50

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
getblocking.com	ns53.domaincontrol.com, ns54.domaincontrol.com	4 records

✅ Authoritative Response

Server:97.74.106.27

NS records: ns53.domaincontrol.com, ns54.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for getblocking.com (unsigned zone)

⏱️ Timing

Total: 1378ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`18.196.70.141`
NS	2	`ns53.domaincontrol.com, ns54.domaincontrol.com`
MX	1	`mail.innade.cloud (pri: 10)`
TXT	2	`v=spf1 mx ~all, google-site-verification=MJVkqr7w4QH38gS`
SOA	1	`ns53.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns53.domaincontrol.com, ns53.domaincontrol.com, ns54.domaincontrol.com...)

Analysis

IP Addresses

getblocking.com has exactly one IP address — 18.196.70.141.

ec2-18-196-70-141.eu-central-1.compute.amazonaws.com and innade.cloud are among other host names that share IP numbers with getblocking.com.

Name Servers

The NS records for getblocking.com delegate to ns53.domaincontrol.com and ns54.domaincontrol.com.

The name server configuration of getblocking.com is shared with other domains, for instance bhhschicago.ai, tolgab.com, hcanimalhealth.com and two others.

getblocking.com and other domains like marionete.co.uk share at least a portion of their name servers.

ns53.domaincontrol.com resolves to 97.74.106.27 and 2603:5:21a2::1b. Likewise, ns54.domaincontrol.com resolves to 173.201.74.27 and 2603:5:22a2::1b — two IP addresses apiece.

Mail Servers

getblocking.com uses one mail server — mail.innade.cloud.

The MX records for getblocking.com match those of other domains — including extensiverewards.com and letsgetmining.com.

getblocking.com partially shares its mail servers with other domains; known examples include bitcoinsfor.me, likecrypto.com and innade.cloud.

The mail servers smtp.s3r3n.com, mail.bitcoinsfor.me and mail-02.innade.cloud are commonly used alongside these mail servers.

mail.innade.cloud resolves to 167.71.39.1 and no other IP number.