🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`authorizebase.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3037::6815:2e34^{🇺🇸 Cloudflare2606:4700:3037::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3037::ac43:dfe0^{🇺🇸 Cloudflare2606:4700:3037::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.46.52^{Cloudflare104.21.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.223.224^{🇺🇸 Cloudflare172.67.208.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`elly.ns.cloudflare.com` ⭐
		A	2606:4700:50::a29f:26f6^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`elly.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c2f6^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`elly.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:22f6^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`elly.ns.cloudflare.com`
		A	108.162.194.246^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`elly.ns.cloudflare.com`
		A	162.159.38.246^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`elly.ns.cloudflare.com`
		A	172.64.34.246^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`elly.ns.cloudflare.com`
NS	`yahir.ns.cloudflare.com`
		A	2606:4700:58::a29f:2c22^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`yahir.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c322^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`yahir.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2322^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`yahir.ns.cloudflare.com`
		A	108.162.195.34^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`yahir.ns.cloudflare.com`
		A	162.159.44.34^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`yahir.ns.cloudflare.com`
		A	172.64.35.34^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`yahir.ns.cloudflare.com`
MX	`route3.mx.cloudflare.net` ⭐
		A	2606:4700:f5::11^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::12^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::13^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.23^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.24^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.25^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
MX	`route1.mx.cloudflare.net`⁽²³⁾
		A	2606:4700:f5::b^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::c^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::d^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.11^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.12^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.13^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
MX	`route2.mx.cloudflare.net`⁽⁸⁷⁾
		A	2606:4700:f5::e^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::f^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::10^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.17^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.18^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.19^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.46.52, 172.67.223.224
		IPv6 hints	2606:4700:3037::6815:2e34, 2606:4700:3037::ac43:dfe0
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=28, name=cloudflare-ech.com
SOA	`elly.ns.cloudflare.com`dns@cloudflare.com serial=2410692144

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

⚠️ On DNS blocklist: tif

Same first word

authorizebase.com

DNS History

9 records (9 active, 0 former)

●NSelly.ns.cloudflare.com2026-06-01 → 2026-08-17 · 2 obs

● 2026-06-01 04:58:54
● 2026-08-17 00:58:16

●NSyahir.ns.cloudflare.com2026-06-01 → 2026-08-17 · 2 obs

● 2026-06-01 04:58:54
● 2026-08-17 00:58:16

●MXroute1.mx.cloudflare.net2026-08-17 → 2026-08-17 · 2 obs

● 2026-08-17 00:58:14
● 2026-08-17 00:58:16

●MXroute2.mx.cloudflare.net2026-08-17 → 2026-08-17 · 2 obs

● 2026-08-17 00:58:14
● 2026-08-17 00:58:16

●MXroute3.mx.cloudflare.net2026-08-17 → 2026-08-17 · 2 obs

● 2026-08-17 00:58:14
● 2026-08-17 00:58:16

●A104.21.46.522026-08-17 → 2026-08-17 · 2 obs

● 2026-08-17 00:58:14
● 2026-08-17 00:58:16

●A172.67.223.2242026-08-17 → 2026-08-17 · 2 obs

● 2026-08-17 00:58:14
● 2026-08-17 00:58:16

●A2606:4700:3037::6815:2e342026-08-17 → 2026-08-17 · 2 obs

● 2026-08-17 00:58:14
● 2026-08-17 00:58:16

●A2606:4700:3037::ac43:dfe02026-08-17 → 2026-08-17 · 2 obs

● 2026-08-17 00:58:14
● 2026-08-17 00:58:16

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	c.gtld-servers.net, i.gtld-servers.net, m.gtld-servers.net, h.gtld-servers.net...	-
authorizebase.com	elly.ns.cloudflare.com, yahir.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.194.246

NS records: elly.ns.cloudflare.com, yahir.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for authorizebase.com (unsigned zone)

⏱️ Timing

Total: 412ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.46.52, 172.67.223.224`
AAAA	2	`2606:4700:3037::ac43:dfe0, 2606:4700:3037::6815:2e34`
NS	2	`elly.ns.cloudflare.com, yahir.ns.cloudflare.com`
MX	3	`route3.mx.cloudflare.net (pri: 13), route1.mx.cloudflare.net (pri: 23)...`
TXT	1	`v=spf1 include:_spf.mx.cloudflare.net ~a`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`elly.ns.cloudflare.com dns.cloudflare.co`

📌 Glue Records Collected

Total: 12

Out-of-bailiwick: 12 (elly.ns.cloudflare.com, elly.ns.cloudflare.com, elly.ns.cloudflare.com...)

Analysis

IP Addresses

authorizebase.com points to the four IP addresses 104.21.46.52, 172.67.223.224, 2606:4700:3037::6815:2e34 and 2606:4700:3037::ac43:dfe0.

sgtm.fixshop.at, allergyboy.com, jesmurphy.com and two other host names share IP numbers with authorizebase.com.

Name Servers

authorizebase.com has two authoritative name servers — elly.ns.cloudflare.com and yahir.ns.cloudflare.com.

authorizebase.com uses the same name servers as several other domains — among them m-fegene-com.pages.dev, klemen.xyz, funhogar.org and two more.

At least some of authorizebase.com's name servers are shared with other domains, for example ettria.com, mypsychconnect.com, eon-mittelland.de and two more.

It is common for these name servers to be used in conjunction with the name servers jasper.ns.cloudflare.com, troy.ns.cloudflare.com and hank.ns.cloudflare.com.

Hostnames that resolve to 6 IP addresses:

elly.ns.cloudflare.com points to 108.162.194.246, 162.159.38.246, 172.64.34.246 and 3 other IP addresses.

yahir.ns.cloudflare.com points to 108.162.195.34, 162.159.44.34, 172.64.35.34 and 3 other IP addresses.

Mail Servers

The MX records for authorizebase.com list three mail servers: route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

authorizebase.com has at least partial mail server overlap with other domains such as arrais.net, schulausfallniedersachsen.de, shorti.us and two more.

Hostnames that resolve to 6 IP addresses:

route1.mx.cloudflare.net points to 162.159.205.11, 162.159.205.12, 162.159.205.13 and 3 other IP addresses.

route2.mx.cloudflare.net points to 162.159.205.17, 162.159.205.18, 162.159.205.19 and 3 other IP addresses.

route3.mx.cloudflare.net points to 162.159.205.23, 162.159.205.24, 162.159.205.25 and 3 other IP addresses.

authorizebase.com - robtex.com