🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`statementparser.ai`

DNSSEC	⚠️ Not signed
A	185.158.133.1^{🇩🇪 Cloudflare185.158.133.0/24}
		PTR	`lovable-app-cd-1-4.p.l5e.io`
NS	`ns-cloud-b1.googledomains.com` ⭐
		A	2001:4860:4802:32::6b^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-b1.googledomains.com`
		A	216.239.32.107^{🇺🇸 Google216.239.32.0/24}
			PTR	`ns-cloud-b1.googledomains.com`
NS	`ns-cloud-b2.googledomains.com`
		A	2001:4860:4802:34::6b^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-b2.googledomains.com`
		A	216.239.34.107^{🇺🇸 Google216.239.34.0/24}
			PTR	`ns-cloud-b2.googledomains.com`
NS	`ns-cloud-b3.googledomains.com`
		A	2001:4860:4802:36::6b^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-b3.googledomains.com`
		A	216.239.36.107^{🇺🇸 Google216.239.36.0/24}
			PTR	`ns-cloud-b3.googledomains.com`
NS	`ns-cloud-b4.googledomains.com`
		A	2001:4860:4802:38::6b^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-b4.googledomains.com`
		A	216.239.38.107^{🇺🇸 Google216.239.38.0/24}
			PTR	`ns-cloud-b4.googledomains.com`
MX	`smtp.google.com` ⭐
		A	2607:f8b0:4004:c08::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bi-in-f26.1e100.net`
		A	2607:f8b0:4004:c09::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bh-in-f27.1e100.net`
		A	2607:f8b0:4004:c1d::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`ww-in-f26.1e100.net`
		A	2607:f8b0:4004:c1d::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`ww-in-f27.1e100.net`
		A	172.253.62.26^{🇺🇸 Google172.253.62.0/24}
			PTR	`bc-in-f26.1e100.net`
		A	172.253.139.27^{🇺🇸 Google172.253.139.0/24}
			PTR	`yuiadsk-in-f27.1e100.net`
		A	192.178.155.26^{🇺🇸 Google192.178.155.0/24}
			PTR	`yuiadrs-in-f26.1e100.net`
		A	192.179.18.26^{🇺🇸 Google192.178.0.0/15}
			PTR	`ry-in-f26.1e100.net`
		A	192.179.18.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`ry-in-f27.1e100.net`
TXT	`google-site-verification=_yL3bLecyhTKAqlKzmDGeqpLVcmmdImHKnEUNfo9swI`
SOA	`ns-cloud-b1.googledomains.com`cloud-dns-hostmaster@google.com serial=1

`ai`

	DNSSEC	🔒 Signed (DS record present)
	NS	`v0n0.nic.ai` ⭐
	NS	`v0n1.nic.ai`
	NS	`v0n2.nic.ai`
	NS	`v0n3.nic.ai`
	NS	`v2n0.nic.ai`
	NS	`v2n1.nic.ai`
	SOA	`v0n0.nic.ai`hostmaster@donuts.email serial=1791197676

Same first word

statementparser.ai

statementparser.com

Similar names

atpterrassement.fr

Previous names

Next names

DNS History

6 records (6 active, 0 former)

●NSns-cloud-b1.googledomains.com2026-09-01 → 2026-10-05 · 2 obs

● 2026-09-01 22:40:42
● 2026-10-05 11:15:12

●NSns-cloud-b2.googledomains.com2026-09-01 → 2026-10-05 · 2 obs

● 2026-09-01 22:40:42
● 2026-10-05 11:15:12

●NSns-cloud-b3.googledomains.com2026-09-01 → 2026-10-05 · 2 obs

● 2026-09-01 22:40:42
● 2026-10-05 11:15:12

●NSns-cloud-b4.googledomains.com2026-09-01 → 2026-10-05 · 2 obs

● 2026-09-01 22:40:42
● 2026-10-05 11:15:12

●MXsmtp.google.com2026-09-01 → 2026-10-05 · 2 obs

● 2026-09-01 22:40:42
● 2026-10-05 11:15:12

●A185.158.133.12026-09-01 → 2026-10-05 · 2 obs

● 2026-09-01 22:40:42
● 2026-10-05 11:15:12

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
ai	v0n0.nic.ai, v0n1.nic.ai, v0n2.nic.ai, v0n3.nic.ai...	12 records
statementparser.ai	ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com	-

✅ Authoritative Response

Server:216.239.38.107

NS records: ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for statementparser.ai (unsigned zone)

⏱️ Timing

Total: 921ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`185.158.133.1`
NS	4	`ns-cloud-b2.googledomains.com, ns-cloud-b1.googledomains.com...`
MX	1	`smtp.google.com (pri: 1)`
TXT	1	`google-site-verification=_yL3bLecyhTKAql`
SOA	1	`ns-cloud-b1.googledomains.com cloud-dns-`

📌 Glue Records Collected

Total: 12

In-bailiwick: 12 (v0n0.nic.ai, v0n0.nic.ai, v0n1.nic.ai...)

Analysis

IP Addresses

statementparser.ai resolves to one IP address: 185.158.133.1.

texasvolleyballschedule.us, www.metrobeauty.ca, somosgestaodeobras.com and two other host names share IP numbers with statementparser.ai.

Name Servers

The authoritative name servers for statementparser.ai are ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com and ns-cloud-b4.googledomains.com.

statementparser.ai has at least partial name server overlap with other domains, such as woodmanproductions.com, draforrest.com, designboy.co and two others.

ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com and ns-cloud-b4.googledomains.com all point to exactly two IP numbers each: ns-cloud-b1.googledomains.com → 216.239.32.107 and 2001:4860:4802:32::6b; ns-cloud-b2.googledomains.com → 216.239.34.107 and 2001:4860:4802:34::6b; ns-cloud-b3.googledomains.com → 216.239.36.107 and 2001:4860:4802:36::6b; ns-cloud-b4.googledomains.com → 216.239.38.107 and 2001:4860:4802:38::6b.

Mail Servers

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

statementparser.ai uses an identical mail server configuration to several other domains — among them gravarservices.com, thelivehouse.net, goclickupengine.pro and two more.

At least some of statementparser.ai's mail servers are shared with other domains, among them saludmichoacan.gob.mx, cap-acp.ca and lnsystems.co.

smtp.google.com resolves to 9 IP addresses — 172.253.62.26, 172.253.139.27, 192.178.155.26 and 6 others.

statementparser.ai - robtex.com