🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`designedfor.com`

DNSSEC	⚠️ Not signed
A	104.156.249.130^{🇺🇸 AS-VULTR104.156.248.0/22 Vultr Assigned Prefix}
		PTR	`104.156.249.130.vultrusercontent.com`
NS	`ns-cloud-a1.googledomains.com` ⭐
		A	2001:4860:4802:32::6a^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-a1.googledomains.com`
		A	216.239.32.106^{🇺🇸 Google216.239.32.0/24}
			PTR	`ns-cloud-a1.googledomains.com`
NS	`ns-cloud-a2.googledomains.com`
		A	2001:4860:4802:34::6a^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-a2.googledomains.com`
		A	216.239.34.106^{🇺🇸 Google216.239.34.0/24}
			PTR	`ns-cloud-a2.googledomains.com`
NS	`ns-cloud-a3.googledomains.com`
		A	2001:4860:4802:36::6a^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-a3.googledomains.com`
		A	216.239.36.106^{🇺🇸 Google216.239.36.0/24}
			PTR	`ns-cloud-a3.googledomains.com`
NS	`ns-cloud-a4.googledomains.com`
		A	2001:4860:4802:38::6a^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-a4.googledomains.com`
		A	216.239.38.106^{🇺🇸 Google216.239.38.0/24}
			PTR	`ns-cloud-a4.googledomains.com`
MX	`friday.mxlogin.com` ⭐
		A	148.251.67.66^{🇩🇪 Hetzner148.251.0.0/16 HETZNER-RZ-BLK-ERX2}
			PTR	`friday.mxlogin.com`
MX	`friday-relay.mxlogin.net`⁽²⁰⁾
TXT	`v=spf1 include:mxlogin.com -all`
SOA	`ns-cloud-a1.googledomains.com`cloud-dns-hostmaster@google.com serial=4

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

Same first word

designedfor.co.uk

designedfor.com

Similar names

frodedesign.com

DNS History

20 records (7 active, 13 former)

●NSns-cloud-a1.googledomains.com2026-04-09 → 2026-08-16 · 3 obs

○ 2017-04-19 23:00:30
● 2026-04-09 08:59:40
● 2026-08-16 04:34:20

●NSns-cloud-a2.googledomains.com2026-04-09 → 2026-08-16 · 3 obs

○ 2017-04-19 23:00:30
● 2026-04-09 08:59:40
● 2026-08-16 04:34:20

●NSns-cloud-a3.googledomains.com2026-04-09 → 2026-08-16 · 3 obs

○ 2017-04-19 23:00:30
● 2026-04-09 08:59:40
● 2026-08-16 04:34:20

●NSns-cloud-a4.googledomains.com2026-04-09 → 2026-08-16 · 3 obs

○ 2017-04-19 23:00:30
● 2026-04-09 08:59:40
● 2026-08-16 04:34:20

○NSns19.domaincontrol.com2008-03-13 → 2008-03-13 · 3 obs

● 2008-03-13 03:30:30
○ 2015-05-29 00:55:24
○ 2026-08-16 04:34:20

○NSns20.domaincontrol.com2008-03-13 → 2008-03-13 · 3 obs

● 2008-03-13 03:30:30
○ 2015-05-29 00:55:24
○ 2026-08-16 04:34:20

○NSns31.domaincontrol.com2015-05-29 → 2017-04-19 · 5 obs

○ 2008-03-13 03:30:30
● 2015-05-29 00:55:24
● 2017-04-19 23:00:30
○ 2026-04-09 08:59:40
○ 2026-08-16 04:34:20

○NSns32.domaincontrol.com2015-05-29 → 2017-04-19 · 5 obs

○ 2008-03-13 03:30:30
● 2015-05-29 00:55:24
● 2017-04-19 23:00:30
○ 2026-04-09 08:59:40
○ 2026-08-16 04:34:20

○MXalt1.aspmx.l.google.com2015-05-29 → 2017-04-19 · 5 obs

○ 2008-03-13 03:30:30
● 2015-05-29 00:55:24
● 2017-04-19 23:00:30
○ 2026-04-09 08:59:40
○ 2026-08-16 04:34:20

○MXalt2.aspmx.l.google.com2015-05-29 → 2017-04-19 · 5 obs

○ 2008-03-13 03:30:30
● 2015-05-29 00:55:24
● 2017-04-19 23:00:30
○ 2026-04-09 08:59:40
○ 2026-08-16 04:34:20

○MXaspmx.l.google.com2015-05-29 → 2017-04-19 · 5 obs

○ 2008-03-13 03:30:30
● 2015-05-29 00:55:24
● 2017-04-19 23:00:30
○ 2026-04-09 08:59:40
○ 2026-08-16 04:34:20

○MXaspmx2.googlemail.com2015-05-29 → 2017-04-19 · 5 obs

○ 2008-03-13 03:30:30
● 2015-05-29 00:55:24
● 2017-04-19 23:00:30
○ 2026-04-09 08:59:40
○ 2026-08-16 04:34:20

○MXaspmx3.googlemail.com2015-05-29 → 2017-04-19 · 5 obs

○ 2008-03-13 03:30:30
● 2015-05-29 00:55:24
● 2017-04-19 23:00:30
○ 2026-04-09 08:59:40
○ 2026-08-16 04:34:20

●MXfriday-relay.mxlogin.net2026-04-09 → 2026-08-16 · 3 obs

○ 2017-04-19 23:00:30
● 2026-04-09 08:59:40
● 2026-08-16 04:34:20

●MXfriday.mxlogin.com2026-04-09 → 2026-08-16 · 3 obs

○ 2017-04-19 23:00:30
● 2026-04-09 08:59:40
● 2026-08-16 04:34:20

○MXmailstore1.secureserver.net2008-03-13 → 2008-03-13 · 3 obs

● 2008-03-13 03:30:30
○ 2015-05-29 00:55:24
○ 2026-08-16 04:34:20

○MXsmtp.secureserver.net2008-03-13 → 2008-03-13 · 3 obs

● 2008-03-13 03:30:30
○ 2015-05-29 00:55:24
○ 2026-08-16 04:34:20

●A104.156.249.1302026-04-09 → 2026-08-16 · 3 obs

○ 2017-04-19 23:00:30
● 2026-04-09 08:59:40
● 2026-08-16 04:34:20

○A184.168.183.12015-05-29 → 2017-04-19 · 5 obs

○ 2008-03-13 03:30:30
● 2015-05-29 00:55:24
● 2017-04-19 23:00:30
○ 2026-04-09 08:59:40
○ 2026-08-16 04:34:20

○A68.178.232.1002008-03-13 → 2008-03-13 · 3 obs

● 2008-03-13 03:30:30
○ 2015-05-29 00:55:24
○ 2026-08-16 04:34:20

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
designedfor.com	ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com	8 records

✅ Authoritative Response

Server:216.239.34.106

NS records: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for designedfor.com (unsigned zone)

⏱️ Timing

Total: 364ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`104.156.249.130`
NS	4	`ns-cloud-a3.googledomains.com, ns-cloud-a2.googledomains.com...`
MX	2	`friday-relay.mxlogin.net (pri: 20), friday.mxlogin.com (pri: 10)`
TXT	1	`v=spf1 include:mxlogin.com -all`
SOA	1	`ns-cloud-a1.googledomains.com cloud-dns-`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns-cloud-a1.googledomains.com, ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com...)

Analysis

IP Addresses

designedfor.com directs to one IP number, which is 104.156.249.130.

Name Servers

The domain designedfor.com is delegated to these four name servers: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com and ns-cloud-a4.googledomains.com.

designedfor.com has at least partial name server overlap with other domains, such as alphawey.com, dhstylingshop.com, benjaminwannercompany.com and two others.

ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com and ns-cloud-a4.googledomains.com all point to exactly two IP numbers each: ns-cloud-a1.googledomains.com → 216.239.32.106 and 2001:4860:4802:32::6a; ns-cloud-a2.googledomains.com → 216.239.34.106 and 2001:4860:4802:34::6a; ns-cloud-a3.googledomains.com → 216.239.36.106 and 2001:4860:4802:36::6a; ns-cloud-a4.googledomains.com → 216.239.38.106 and 2001:4860:4802:38::6a.

Mail Servers

The MX records for designedfor.com point to two mail servers: friday.mxlogin.com and friday-relay.mxlogin.net.

designedfor.com shares at least some of its mail servers with other domains — for example btggaming.com, postercollector.co.uk, tarasis.net and two more.

It is common to find these mail servers paired with the mail servers friday-relay.mxlogin.com.

Hosts that resolve to one IP address:

friday.mxlogin.com resolves to 148.251.67.66.

designedfor.com - robtex.com

designedfor.com

com

Same first word

Similar names

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

📌 Glue Records Collected

Analysis

IP Addresses

Name Servers

Mail Servers

`designedfor.com`

`com`