🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`integer32.com`

DNSSEC	⚠️ Not signed
A	2600:1901:0:7b8a::^{🇺🇸 Google2600:1901::/32}
A	35.185.44.232^{🇺🇸 Google35.185.32.0/20}
NS	`ns1.dnsimple.com` ⭐
		A	2620:111:8004::53^{🇺🇸 AS327712620:111:8004::/48 DNSimple Corporation}
		A	199.247.152.53^{🇺🇸 AS32771199.247.152.0/24 DNSimple Corporation}
NS	`ns2.dnsimple.com`
		A	2620:111:8005::53^{🇺🇸 AS327712620:111:8005::/48 Vultr Customer Route}
		A	199.247.153.53^{🇺🇸 AS32771199.247.153.0/24 Vultr Customer Route}
NS	`ns3.dnsimple.com`
		A	2620:111:8006::53^{🇺🇸 AS327712620:111:8006::/48 DNSimple Corporation}
		A	199.247.154.53^{🇺🇸 AS32771199.247.154.0/24 DNSimple Corporation}
NS	`ns4.dnsimple.com`
		A	2620:111:8007::53^{🇺🇸 AS327712620:111:8007::/48 Vultr Customer Route}
		A	199.247.155.53^{🇺🇸 AS32771199.247.155.0/24 Vultr Customer Route}
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c23::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadrs-in-f26.1e100.net`
		A	64.233.180.27^{🇺🇸 Google64.233.180.0/24}
			PTR	`on-in-f27.1e100.net`
			PTR	`pe-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.26^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.1e100.net`
		A	192.178.223.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1b^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f27.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`v=spf1 include:_spf.google.com include:mailgun.org include:servers.mcsv.net ~all`
SOA	`ns1.dnsimple.com`admin@dnsimple.com serial=1466086419

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

Same first word

integer32.com

Previous names

Next names

DNS History

30 records (11 active, 19 former)

○NSdns1.registrar-servers.com2016-05-03 → 2016-05-03 · 4 obs

○ 2015-11-15 11:30:18
● 2016-05-03 16:08:24
○ 2017-02-03 20:31:56
○ 2026-09-02 07:43:50

○NSdns11.parkpage.foundationapi.com2015-07-10 → 2015-07-10 · 3 obs

● 2015-07-10 09:35:12
○ 2015-11-15 11:30:18
○ 2026-09-02 07:43:50

○NSdns12.parkpage.foundationapi.com2015-07-10 → 2015-07-10 · 3 obs

● 2015-07-10 09:35:12
○ 2015-11-15 11:30:18
○ 2026-09-02 07:43:50

○NSdns2.registrar-servers.com2016-05-03 → 2016-05-03 · 4 obs

○ 2015-11-15 11:30:18
● 2016-05-03 16:08:24
○ 2017-02-03 20:31:56
○ 2026-09-02 07:43:50

○NSdns3.registrar-servers.com2016-05-03 → 2016-05-03 · 4 obs

○ 2015-11-15 11:30:18
● 2016-05-03 16:08:24
○ 2017-02-03 20:31:56
○ 2026-09-02 07:43:50

○NSdns4.registrar-servers.com2016-05-03 → 2016-05-03 · 4 obs

○ 2015-11-15 11:30:18
● 2016-05-03 16:08:24
○ 2017-02-03 20:31:56
○ 2026-09-02 07:43:50

○NSdns5.registrar-servers.com2016-05-03 → 2016-05-03 · 4 obs

○ 2015-11-15 11:30:18
● 2016-05-03 16:08:24
○ 2017-02-03 20:31:56
○ 2026-09-02 07:43:50

○NSdns9.parkpage.foundationapi.com2015-07-10 → 2015-07-10 · 3 obs

● 2015-07-10 09:35:12
○ 2015-11-15 11:30:18
○ 2026-09-02 07:43:50

●NSns1.dnsimple.com2017-02-03 → 2026-09-02 · 3 obs

○ 2016-05-03 16:08:24
● 2017-02-03 20:31:56
● 2026-09-02 07:43:50

●NSns2.dnsimple.com2017-02-03 → 2026-09-02 · 3 obs

○ 2016-05-03 16:08:24
● 2017-02-03 20:31:56
● 2026-09-02 07:43:50

●NSns3.dnsimple.com2017-02-03 → 2026-09-02 · 3 obs

○ 2016-05-03 16:08:24
● 2017-02-03 20:31:56
● 2026-09-02 07:43:50

●NSns4.dnsimple.com2017-02-03 → 2026-09-02 · 3 obs

○ 2016-05-03 16:08:24
● 2017-02-03 20:31:56
● 2026-09-02 07:43:50

●MXalt1.aspmx.l.google.com2026-08-19 → 2026-09-02 · 3 obs

○ 2017-02-03 20:31:56
● 2026-08-19 17:06:36
● 2026-09-02 07:43:50

●MXalt2.aspmx.l.google.com2026-08-19 → 2026-09-02 · 3 obs

○ 2017-02-03 20:31:56
● 2026-08-19 17:06:36
● 2026-09-02 07:43:50

●MXalt3.aspmx.l.google.com2026-08-19 → 2026-09-02 · 3 obs

○ 2017-02-03 20:31:56
● 2026-08-19 17:06:36
● 2026-09-02 07:43:50

●MXalt4.aspmx.l.google.com2026-08-19 → 2026-09-02 · 3 obs

○ 2017-02-03 20:31:56
● 2026-08-19 17:06:36
● 2026-09-02 07:43:50

●MXaspmx.l.google.com2026-08-19 → 2026-09-02 · 3 obs

○ 2017-02-03 20:31:56
● 2026-08-19 17:06:36
● 2026-09-02 07:43:50

○MXeforward1.registrar-servers.com2016-05-03 → 2016-05-03 · 3 obs

● 2016-05-03 16:08:24
○ 2017-02-03 20:31:56
○ 2026-09-02 07:43:50

○MXeforward2.registrar-servers.com2016-05-03 → 2016-05-03 · 3 obs

● 2016-05-03 16:08:24
○ 2017-02-03 20:31:56
○ 2026-09-02 07:43:50

○MXeforward3.registrar-servers.com2016-05-03 → 2016-05-03 · 3 obs

● 2016-05-03 16:08:24
○ 2017-02-03 20:31:56
○ 2026-09-02 07:43:50

○MXeforward4.registrar-servers.com2016-05-03 → 2016-05-03 · 3 obs

● 2016-05-03 16:08:24
○ 2017-02-03 20:31:56
○ 2026-09-02 07:43:50

○MXeforward5.registrar-servers.com2016-05-03 → 2016-05-03 · 3 obs

● 2016-05-03 16:08:24
○ 2017-02-03 20:31:56
○ 2026-09-02 07:43:50

○MXmxa.mailgun.org2017-02-03 → 2017-02-03 · 4 obs

○ 2016-05-03 16:08:24
● 2017-02-03 20:31:56
○ 2026-08-19 17:06:36
○ 2026-09-02 07:43:50

○MXmxb.mailgun.org2017-02-03 → 2017-02-03 · 4 obs

○ 2016-05-03 16:08:24
● 2017-02-03 20:31:56
○ 2026-08-19 17:06:36
○ 2026-09-02 07:43:50

○A104.208.235.322017-02-03 → 2017-02-03 · 4 obs

○ 2016-05-03 16:08:24
● 2017-02-03 20:31:56
○ 2026-08-19 17:06:36
○ 2026-09-02 07:43:50

○A162.255.119.2502016-05-03 → 2016-05-03 · 4 obs

○ 2015-11-15 11:30:18
● 2016-05-03 16:08:24
○ 2017-02-03 20:31:56
○ 2026-09-02 07:43:50

○A209.99.40.2222015-07-10 → 2015-07-10 · 3 obs

● 2015-07-10 09:35:12
○ 2015-11-15 11:30:18
○ 2026-09-02 07:43:50

○A209.99.40.2232015-07-10 → 2015-07-10 · 3 obs

● 2015-07-10 09:35:12
○ 2017-02-03 20:31:56
○ 2026-09-02 07:43:50

●A2600:1901:0:7b8a::2026-08-19 → 2026-09-02 · 3 obs

○ 2017-02-03 20:31:56
● 2026-08-19 17:06:36
● 2026-09-02 07:43:50

●A35.185.44.2322026-08-19 → 2026-09-02 · 3 obs

○ 2017-02-03 20:31:56
● 2026-08-19 17:06:36
● 2026-09-02 07:43:50

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
integer32.com	ns1.dnsimple.com, ns2.dnsimple.com, ns3.dnsimple.com, ns4.dnsimple.com	8 records

✅ Authoritative Response

Server:199.247.152.53

NS records: ns1.dnsimple.com, ns2.dnsimple.com, ns3.dnsimple.com, ns4.dnsimple.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for integer32.com (unsigned zone)

⏱️ Timing

Total: 903ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`35.185.44.232`
AAAA	1	`2600:1901:0:7b8a::`
NS	4	`ns1.dnsimple.com, ns2.dnsimple.com...`
MX	5	`aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...`
TXT	1	`v=spf1 include:_spf.google.com include:m`
SOA	1	`ns1.dnsimple.com admin.dnsimple.com`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns1.dnsimple.com, ns1.dnsimple.com, ns2.dnsimple.com...)

Analysis

IP Addresses

integer32.com directs to two IP numbers, 35.185.44.232 and 2600:1901:0:7b8a::

kwam.es, trendforum.nl, bricksoft.org plus two other host names have IP numbers in common with integer32.com.

Name Servers

Four name servers handle the delegation for integer32.com: ns1.dnsimple.com, ns2.dnsimple.com, ns3.dnsimple.com and ns4.dnsimple.com.

integer32.com partially shares its NS delegation with several other domains, including goenrollatnorthamericanmed.com, fulfildash.com, piccologourmet.com and two others.

The name servers ns4.dnsimple-edge.org, ns2.dnsimple-edge.net, ns1.dnsimple-edge.com and ns3.dnsimple-edge.io are often found in use alongside these name servers.

ns1.dnsimple.com, ns2.dnsimple.com, ns3.dnsimple.com and ns4.dnsimple.com each carry two IP addresses. ns1.dnsimple.com has 199.247.152.53 and 2620:111:8004::53; ns2.dnsimple.com has 199.247.153.53 and 2620:111:8005::53; ns3.dnsimple.com has 199.247.154.53 and 2620:111:8006::53; ns4.dnsimple.com has 199.247.155.53 and 2620:111:8007::53.

Mail Servers

Mail for integer32.com is handled by five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

At least some of the mail servers used by integer32.com are shared with other domains: hamiltonfamily.name, cabrerasweb.com, www.everyday.agency and two others among them.

These mail servers are often deployed together with alt4.aspmx.l.google.com, alt3.aspmx.l.google.com, aspmx2.googlemail.com and 3 other mail servers.

Host names pointing to two IP addresses:

aspmx.l.google.com resolves to 64.233.180.27 and 2607:f8b0:4004:c23::1a.

alt1.aspmx.l.google.com resolves to 192.178.234.26 and 2800:3f0:4003:c14::1b.

alt2.aspmx.l.google.com resolves to 172.253.116.27 and 2a00:1450:400b:c02::1b.

alt3.aspmx.l.google.com resolves to 192.178.223.26 and 2a00:1450:4009:c0f::1b.

alt4.aspmx.l.google.com resolves to 172.253.157.27 and 2a00:1450:400c:c23::1b.