🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`poly3d.in`

DNSSEC	⚠️ Not signed
A	2606:4700:3035::6815:1543^{🇺🇸 Cloudflare2606:4700:3035::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3036::ac43:c4cf^{🇺🇸 Cloudflare2606:4700:3036::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.21.67^{Cloudflare104.21.16.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.196.207^{🇺🇸 Cloudflare172.67.192.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`dakota.ns.cloudflare.com` ⭐
		A	2606:4700:58::a29f:2c4f^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`dakota.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c34f^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`dakota.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:234f^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`dakota.ns.cloudflare.com`
		A	108.162.195.79^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`dakota.ns.cloudflare.com`
		A	162.159.44.79^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`dakota.ns.cloudflare.com`
		A	172.64.35.79^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`dakota.ns.cloudflare.com`
NS	`poppy.ns.cloudflare.com`
		A	2606:4700:50::a29f:2621^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`poppy.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c221^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`poppy.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2221^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`poppy.ns.cloudflare.com`
		A	108.162.194.33^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`poppy.ns.cloudflare.com`
		A	162.159.38.33^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`poppy.ns.cloudflare.com`
		A	172.64.34.33^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`poppy.ns.cloudflare.com`
MX	`mx1.hostinger.com` ⭐
		A	2606:4700:90:0:c1f8:f874:2386:b61f^{🇺🇸 Cloudflare2606:4700:90::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
		A	172.65.182.103^{🇺🇸 Cloudflare172.65.176.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
MX	`mx2.hostinger.com`⁽¹⁰⁾
		A	2606:4700:90:0:c1f8:f874:2386:b61f^{🇺🇸 Cloudflare2606:4700:90::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
		A	172.65.182.103^{🇺🇸 Cloudflare172.65.176.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
TXT	`v=spf1 include:_spf.mail.hostinger.com ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.21.67, 172.67.196.207
		IPv6 hints	2606:4700:3035::6815:1543, 2606:4700:3036::ac43:c4cf
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=66, name=cloudflare-ech.com
SOA	`dakota.ns.cloudflare.com`dns@cloudflare.com serial=2411791372

`in`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns.trs-dns.com` ⭐
	NS	`ns1.registry.in`
	NS	`ns2.registry.in`
	NS	`ns3.registry.in`
	NS	`ns4.registry.in`
	SOA	`ns.trs-dns.com`trs-ops@tucows.com serial=1786977660

Same first word

poly3d.in

poly3d.com

poly3d.com.hk

Similar names

d3ploy.com

3dpoly.com

Nearby domains

previous 10	`poly2010.in`, `poly-sure.in`, `poly-clip.in`, `poly.in`, `polvo.in`, `polvent.in`, `polux.in`, `polussoftware.in`, `polus.in`, `polur.in`
next 10	`polyadmission.in`, `polyamp.in`, `polyaniline.in`, `polyapple.in`, `polyarch.in`, `polyart.in`, `polybest.in`, `polybion.in`, `polybond.in`, `polyc.in`

DNS History

8 records (8 active, 0 former)

●NSdakota.ns.cloudflare.com2026-08-13 → 2026-08-17 · 2 obs

● 2026-08-13 10:10:24
● 2026-08-17 15:00:44

●NSpoppy.ns.cloudflare.com2026-08-13 → 2026-08-17 · 2 obs

● 2026-08-13 10:10:24
● 2026-08-17 15:00:44

●MXmx1.hostinger.com2026-08-13 → 2026-08-17 · 2 obs

● 2026-08-13 10:10:24
● 2026-08-17 15:00:44

●MXmx2.hostinger.com2026-08-13 → 2026-08-17 · 2 obs

● 2026-08-13 10:10:24
● 2026-08-17 15:00:44

●A104.21.21.672026-08-13 → 2026-08-17 · 2 obs

● 2026-08-13 10:10:24
● 2026-08-17 15:00:44

●A172.67.196.2072026-08-13 → 2026-08-17 · 2 obs

● 2026-08-13 10:10:24
● 2026-08-17 15:00:44

●A2606:4700:3035::6815:15432026-08-13 → 2026-08-17 · 2 obs

● 2026-08-13 10:10:24
● 2026-08-17 15:00:44

●A2606:4700:3036::ac43:c4cf2026-08-13 → 2026-08-17 · 2 obs

● 2026-08-13 10:10:24
● 2026-08-17 15:00:44

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
in	ns1.registry.in, ns2.registry.in, ns3.registry.in, ns4.registry.in	8 records
poly3d.in	dakota.ns.cloudflare.com, poppy.ns.cloudflare.com	-

✅ Authoritative Response

Server:108.162.194.33

NS records: dakota.ns.cloudflare.com, poppy.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for poly3d.in (unsigned zone)

⏱️ Timing

Total: 243ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.67.196.207, 104.21.21.67`
AAAA	2	`2606:4700:3036::ac43:c4cf, 2606:4700:3035::6815:1543`
NS	2	`dakota.ns.cloudflare.com, poppy.ns.cloudflare.com`
MX	2	`mx2.hostinger.com (pri: 10), mx1.hostinger.com (pri: 5)`
TXT	1	`v=spf1 include:_spf.mail.hostinger.com ~`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`dakota.ns.cloudflare.com dns.cloudflare.`

📌 Glue Records Collected

Total: 8

In-bailiwick: 8 (ns1.registry.in, ns1.registry.in, ns2.registry.in...)

Analysis

IP Addresses

poly3d.in points to the four IP addresses 104.21.21.67, 172.67.196.207, 2606:4700:3035::6815:1543 and 2606:4700:3036::ac43:c4cf.

www.departementfeminin.com, amadeosmenu.com, sj-london.net and two other host names share IP numbers with poly3d.in.

Name Servers

poly3d.in is delegated to two name servers: dakota.ns.cloudflare.com and poppy.ns.cloudflare.com.

poly3d.in uses the same name servers as several other domains — among them nachdom.ru, healthworks360.com, patchtimer.org and two more.

There is at least partial name server overlap between poly3d.in and other domains — adlemx.ru, hnsfl.com, leadership-possibilities.com and two more among them.

It is common to find these name servers alongside the name servers nadia.ns.cloudflare.com, stan.ns.cloudflare.com, izabella.ns.cloudflare.com and two others.

Hostnames that resolve to 6 IP addresses:

dakota.ns.cloudflare.com resolves to 108.162.195.79, 162.159.44.79, 172.64.35.79 and 3 other IP addresses.

poppy.ns.cloudflare.com resolves to 108.162.194.33, 162.159.38.33, 172.64.34.33 and 3 other IP addresses.

Mail Servers

Mail for poly3d.in is handled by two mail servers — mx1.hostinger.com and mx2.hostinger.com.

poly3d.in uses an identical mail server configuration to several other domains — among them butterflysilkart.com, voluta.gt, visaooeste.com.br and two more.

poly3d.in and other domains — interracialmatching.com for instance — share at least some mail servers.

mx1.hostinger.com and mx2.hostinger.com each resolve to two IP addresses: 172.65.182.103 and 2606:4700:90:0:c1f8:f874:2386:b61f.

mx1.hostinger.com and mx2.hostinger.com are host names that each point to 2606:4700:90:0:c1f8:f874:2386:b61f IP addresses.

mx1.hostinger.com and mx2.hostinger.com are host names that each point to 172.65.182.103 IP addresses.

poly3d.in - robtex.com

poly3d.in

in

Same first word

Similar names

Nearby domains

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

📌 Glue Records Collected

Analysis

IP Addresses

Name Servers

Mail Servers

`poly3d.in`

`in`