Skip to content

Hostname

connect2central.com

Last fetched

connect2central.com resolves to 162.0.212.4, announced in 162.0.212.0/24 by NAMECHEAP-NET - Namecheap, Inc. in US. connect2central.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · connect2central.comRouting diversity1.5/10Peering density4.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/connect2central.com

Resolution chain

IPv6 resolution

No AAAA record for connect2central.com is recorded in WhisperGraph.

Attribution

namecheap

ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
central baptist church
Contact emails
connect2centralbaptist@gmail.com, 389491762632456094c1c842a23ac88c.protect@whoisguard.com, ab24c9de93964caba01c7de8cf54ae28.protect@whoisguard.com, 1fc5a4a4e8354fd5a6b6f127a4732e47.protect@withheldforprivacy.com

Subdomains

Subdomain
www.connect2central.com

Showing 1 of 1 subdomain (1 per page).

Mail and authentication

Nameservers

  • dns1.registrar-servers.com
  • dns2.registrar-servers.com
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net
  • ns0.wixdns.net
  • ns1.wixdns.net

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • include: _spf.google.com

Threat-feed evidence

History

Related pages

Pivot from connect2central.com into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "connect2central.com"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.