🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`bytesingularity.com`

DNSSEC	⚠️ Not signed
A	143.244.202.151^{🇺🇸 DIGITALOCEAN143.244.200.0/22 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`
		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	`smtp.google.com` ⭐
		A	2607:f8b0:4004:c06::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bg-in-f26.1e100.net`
		A	2607:f8b0:4004:c06::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bg-in-f27.1e100.net`
		A	2607:f8b0:4004:c23::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadrs-in-f26.1e100.net`
		A	2607:f8b0:4004:c23::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadrs-in-f27.1e100.net`
		A	172.253.115.26^{🇺🇸 Google172.253.115.0/24}
			PTR	`bg-in-f26.1e100.net`
		A	172.253.115.27^{🇺🇸 Google172.253.115.0/24}
			PTR	`bg-in-f27.1e100.net`
		A	172.253.122.27^{🇺🇸 Google172.253.122.0/24}
			PTR	`bh-in-f27.1e100.net`
		A	192.178.155.26^{🇺🇸 Google192.178.155.0/24}
			PTR	`yuiadrs-in-f26.1e100.net`
		A	192.178.155.27^{🇺🇸 Google192.178.155.0/24}
			PTR	`yuiadrs-in-f27.1e100.net`
TXT	`google-site-verification=o4CIHEDfPFIOOQCRk3wBrWpeRu8V04dy1ZG9L9TrBXM`
SOA	`ns1.digitalocean.com`hostmaster@bytesingularity.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=1788869898

Same first word

bytesingularity.com

Previous names

Next names

DNS History

5 records (5 active, 0 former)

●NSns1.digitalocean.com2026-08-29 → 2026-09-08 · 2 obs

● 2026-08-29 21:51:20
● 2026-09-08 12:41:54

●NSns2.digitalocean.com2026-08-29 → 2026-09-08 · 2 obs

● 2026-08-29 21:51:20
● 2026-09-08 12:41:54

●NSns3.digitalocean.com2026-08-29 → 2026-09-08 · 2 obs

● 2026-08-29 21:51:20
● 2026-09-08 12:41:54

●MXsmtp.google.com2026-08-29 → 2026-09-08 · 2 obs

● 2026-08-29 21:51:20
● 2026-09-08 12:41:54

●A143.244.202.1512026-08-29 → 2026-09-08 · 2 obs

● 2026-08-29 21:51:20
● 2026-09-08 12:41:54

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	k.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, i.gtld-servers.net...	-
bytesingularity.com	ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com	3 records

✅ Authoritative Response

Server:172.64.52.210

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for bytesingularity.com (unsigned zone)

⏱️ Timing

Total: 360ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`143.244.202.151`
NS	3	`ns2.digitalocean.com, ns1.digitalocean.com...`
MX	1	`smtp.google.com (pri: 1)`
TXT	1	`google-site-verification=o4CIHEDfPFIOOQC`
SOA	1	`ns1.digitalocean.com hostmaster.bytesing`

📌 Glue Records Collected

Total: 3

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

Analysis

IP Addresses

bytesingularity.com resolves to one IP address: 143.244.202.151.

Name Servers

bytesingularity.com is delegated to three name servers: ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com.

There is at least partial name server overlap between bytesingularity.com and other domains — 188.209.134.in-addr.arpa, graphiscomunicacao.com.br, casheddy.es and two more among them.

ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com each resolve to two IP addresses: ns1.digitalocean.com resolves to 172.64.52.210 and 2606:4700:52::ac40:34d2; ns2.digitalocean.com resolves to 172.64.53.21 and 2606:4700:5a::ac40:3515; ns3.digitalocean.com resolves to 172.64.49.209 and 2606:4700:52::ac40:31d1.

Mail Servers

Mail for bytesingularity.com is handled by a single mail server, smtp.google.com.

bytesingularity.com uses an identical mail server configuration to several other domains — among them rivetbay.com, newhampfixit.com, for-loop.com and two more.

bytesingularity.com has at least partial mail server overlap with other domains such as yalidesign.com, myma.us, northcastrise.info and two more.

smtp.google.com resolves to 9 IP addresses — 172.253.115.26, 172.253.115.27, 172.253.122.27 and 6 others.

bytesingularity.com - robtex.com