infobells.com - robtex.com

infobells.com

DNSSEC⚠️ Not signed
A148.66.136.66πŸ‡ΈπŸ‡¬ GODADDY148.66.136.0/22 Godaddy.com 80 Robinson Road 02-00
PTR66.136.66.148.host.secureserver.net
NSns35.domaincontrol.com ⭐
A2603:5:21b1::12πŸ‡ΊπŸ‡Έ GODADDY-DNS2603:5:21b0::/44
PTRns35.domaincontrol.com
A97.74.107.18πŸ‡ΊπŸ‡Έ GODADDY-DNS97.74.106.0/23
PTRns35.domaincontrol.com
NSns36.domaincontrol.com
A2603:5:22b1::12πŸ‡ΊπŸ‡Έ GODADDY-DNS2603:5:22b0::/44
PTRns36.domaincontrol.com
A173.201.75.18πŸ‡ΊπŸ‡Έ GODADDY-DNS173.201.74.0/23
PTRns36.domaincontrol.com
MXaspmx.l.google.com ⭐
A2607:f8b0:4004:c19::1bπŸ‡ΊπŸ‡Έ Google2607:f8b0:4004::/48
PTRbk-in-f27.1e100.net
A172.253.62.27πŸ‡ΊπŸ‡Έ Google172.253.62.0/24
PTRbc-in-f27.1e100.net
MXalt1.aspmx.l.google.com(5)
A2607:f8b0:4003:c30::1bπŸ‡ΊπŸ‡Έ Google2607:f8b0:4003::/48
PTRyutulis-in-f27.1e100.net
A74.125.27.26πŸ‡ΊπŸ‡Έ Google74.125.27.0/24
PTRyutulis-in-f26.1e100.net
MXalt2.aspmx.l.google.com(5)
A2607:f8b0:4001:c70::1aπŸ‡ΊπŸ‡Έ Google2607:f8b0:4001::/48
PTRyucbful-in-f26.1e100.net
A192.178.209.26πŸ‡ΊπŸ‡Έ Google192.178.209.0/24
PTRyucbful-in-f26.1e100.net
MXalt3.aspmx.l.google.com(10)
A2607:f8b0:4024:c0d::1bπŸ‡ΊπŸ‡Έ Google2607:f8b0::/32
PTRmj-in-f27.1e100.net
A192.178.152.26πŸ‡ΊπŸ‡Έ Google192.178.152.0/24
PTRmj-in-f26.1e100.net
MXalt4.aspmx.l.google.com(10)
A2607:f8b0:4023:403::1aπŸ‡ΊπŸ‡Έ Google2607:f8b0::/32
PTRgg-in-f26.1e100.net
A142.250.96.27πŸ‡ΊπŸ‡Έ Google142.250.96.0/24
PTRgg-in-f27.1e100.net
TXTv=spf1 include:_spf.google.com ~all
SOAns35.domaincontrol.comdns@jomax.net 2021-05-13 #0

com

Same first word

Similar names

DNS History

17 records (8 active, 9 former)

20162017201820192020202120222023202420252026NSns35.domaincontrol.comns36.domaincontrol.comns1.net4india.comns11.hostingraja.inns12.hostingraja.inns15.hostingraja.inns16.hostingraja.inns2.net4india.comMXalt1.aspmx.l.google.comalt2.aspmx.l.google.comalt3.aspmx.l.google.comalt4.aspmx.l.google.comaspmx.l.google.cominfobells.comA148.66.136.66103.241.147.67202.143.99.106
β—‹NSns1.net4india.com2016-09-26 β†’ 2017-10-16 Β· 4 obs
β—‹ 2016-08-20 00:23:28
● 2016-09-26 19:36:52
● 2017-10-16 08:03:06
β—‹ 2026-03-15 06:51:24
β—‹NSns11.hostingraja.in2015-08-29 β†’ 2016-08-20 Β· 4 obs
● 2015-08-29 11:54:10
● 2016-08-20 00:23:28
β—‹ 2016-09-26 19:36:52
β—‹ 2026-03-15 06:51:24
β—‹NSns12.hostingraja.in2015-08-29 β†’ 2016-08-20 Β· 4 obs
● 2015-08-29 11:54:10
● 2016-08-20 00:23:28
β—‹ 2016-09-26 19:36:52
β—‹ 2026-03-15 06:51:24
β—‹NSns15.hostingraja.in2015-08-29 β†’ 2016-08-20 Β· 4 obs
● 2015-08-29 11:54:10
● 2016-08-20 00:23:28
β—‹ 2016-09-26 19:36:52
β—‹ 2026-03-15 06:51:24
β—‹NSns16.hostingraja.in2015-08-29 β†’ 2016-08-20 Β· 4 obs
● 2015-08-29 11:54:10
● 2016-08-20 00:23:28
β—‹ 2016-09-26 19:36:52
β—‹ 2026-03-15 06:51:24
β—‹NSns2.net4india.com2016-09-26 β†’ 2017-10-16 Β· 4 obs
β—‹ 2016-08-20 00:23:28
● 2016-09-26 19:36:52
● 2017-10-16 08:03:06
β—‹ 2026-03-15 06:51:24
●NSns35.domaincontrol.com2026-03-15 β†’ 2026-03-15 Β· 2 obs
β—‹ 2017-10-16 08:03:06
● 2026-03-15 06:51:24
●NSns36.domaincontrol.com2026-03-15 β†’ 2026-03-15 Β· 2 obs
β—‹ 2017-10-16 08:03:06
● 2026-03-15 06:51:24
●MXalt1.aspmx.l.google.com2016-09-26 β†’ 2026-03-15 Β· 3 obs
β—‹ 2016-08-20 00:23:28
● 2016-09-26 19:36:52
● 2026-03-15 06:51:24
●MXalt2.aspmx.l.google.com2016-09-26 β†’ 2026-03-15 Β· 3 obs
β—‹ 2016-08-20 00:23:28
● 2016-09-26 19:36:52
● 2026-03-15 06:51:24
●MXalt3.aspmx.l.google.com2026-03-15 β†’ 2026-03-15 Β· 2 obs
β—‹ 2016-09-26 19:36:52
● 2026-03-15 06:51:24
●MXalt4.aspmx.l.google.com2026-03-15 β†’ 2026-03-15 Β· 2 obs
β—‹ 2016-09-26 19:36:52
● 2026-03-15 06:51:24
●MXaspmx.l.google.com2016-09-26 β†’ 2026-03-15 Β· 3 obs
β—‹ 2016-08-20 00:23:28
● 2016-09-26 19:36:52
● 2026-03-15 06:51:24
β—‹MXinfobells.com2015-08-29 β†’ 2016-08-20 Β· 4 obs
● 2015-08-29 11:54:10
● 2016-08-20 00:23:28
β—‹ 2016-09-26 19:36:52
β—‹ 2026-03-15 06:51:24
β—‹A103.241.147.672015-08-29 β†’ 2016-08-20 Β· 4 obs
● 2015-08-29 11:54:10
● 2016-08-20 00:23:28
β—‹ 2016-09-26 19:36:52
β—‹ 2026-03-15 06:51:24
●A148.66.136.662017-08-19 β†’ 2026-03-15 Β· 3 obs
β—‹ 2017-07-29 20:30:12
● 2017-08-19 13:02:22
● 2026-03-15 06:51:24
β—‹A202.143.99.1062016-09-26 β†’ 2017-07-29 Β· 5 obs
β—‹ 2016-08-20 00:23:28
● 2016-09-26 19:36:52
● 2017-07-29 20:30:12
β—‹ 2017-08-19 13:02:22
β—‹ 2026-03-15 06:51:24

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
coml.gtld-servers.net, j.gtld-servers.net, c.gtld-servers.net, b.gtld-servers.net...-
infobells.comns35.domaincontrol.com, ns36.domaincontrol.com4 records

βœ… Authoritative Response

Server: 97.74.107.18

NS records: ns35.domaincontrol.com, ns36.domaincontrol.com

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for infobells.com (unsigned zone)

⏱️ Timing

Total: 191ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A1148.66.136.66
NS2ns35.domaincontrol.com, ns36.domaincontrol.com
MX5alt1.aspmx.l.google.com (pri: 5), alt2.aspmx.l.google.com (pri: 5)...
TXT1v=spf1 include:_spf.google.com ~all
SOA1ns35.domaincontrol.com dns.jomax.net

πŸ“Œ Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns35.domaincontrol.com, ns35.domaincontrol.com, ns36.domaincontrol.com...)

Analysis

IP Addresses

infobells.com points to IP number 148.66.136.66.

For instance, other host names nemimatrimony.com, mail.dikoli.com, mail.rajeevedu.in, 66.136.66.148.host.secureserver.net and alorcorp.com share IP numbers with infobells.com.

Name Servers

infobells.com is delegated to two name servers: ns35.domaincontrol.com and ns36.domaincontrol.com.

infobells.com uses the same name server setup as other domains such as cashforpinkslip.net, risephone.com, chisca.info, cnptv.com and violetsupply.com.

Host names with two IP numbers:

ns35.domaincontrol.com points to 2603:5:21b1::12 and 97.74.107.18; ns36.domaincontrol.com points to 2603:5:22b1::12 and 173.201.75.18.

Mail Servers

Five mail servers handle infobells.com: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com.

infobells.com shares mail servers with other domains at least partially; for instance ns500768.ns500758.ns500698.ns500758.ns500736.ns500698.ns500736.ns500735.ns500735.ns500735.ns500576.ns500619.ns500576.ns500576.ns500576.trackreceptor.com, ns500765.ns500693.ns500693.ns500699.ns500734.ns500699.ns500693.ns500699.ns500699.ns500699.ns500588.ns500683.ns500699.ns500588.ns500699.ns500693.ns500602.dtrkdll.com, ns500765.ns500699.ns500699.ns500734.ns500699.ns500699.ns500693.ns500693.ns500693.ns500588.ns500683.ns500683.ns500612.ns500612.ns500578.ns500110.dtrkdll.com, ns500768.ns500758.ns500758.ns500759.ns500758.ns500758.ns500698.ns500735.ns500698.ns500735.ns500736.ns500576.ns500698.ns500576.ns500619.ns500619.trackreceptor.com and ns500699.ns500765.ns500765.ns500693.ns500734.ns500693.ns500693.ns500699.ns500693.ns500693.ns500699.ns500683.ns500632.ns500632.dtrkdll.com.

these mail servers are commonly used alongside aspmx2.googlemail.com and aspmx3.googlemail.com.

Host names with two IP numbers:

aspmx.l.google.com points to 2607:f8b0:4004:c19::1b and 172.253.62.27

alt1.aspmx.l.google.com points to 2607:f8b0:4003:c30::1b and 74.125.27.26

alt2.aspmx.l.google.com points to 2607:f8b0:4001:c70::1a and 192.178.209.26

alt3.aspmx.l.google.com points to 2607:f8b0:4024:c0d::1b and 192.178.152.26

alt4.aspmx.l.google.com points to 2607:f8b0:4023:403::1a and 142.250.96.27