Skip to content

Hostname

wizcom.co

Last fetched

wizcom.co resolves to 100.28.32.149, announced in 100.24.0.0/13 by AMAZON-AES - Amazon.com, Inc. in US. wizcom.co 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 · wizcom.coRouting diversity2.4/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.5/10canon.whisper.security/host/wizcom.co

Resolution chain

IPv6 resolution

No AAAA record for wizcom.co is recorded in WhisperGraph.

Attribution

Aws

cloud · MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:146
Registrant organisation
domains by proxy,

Subdomains

Subdomain
autodiscover.wizcom.co
cpanel.wizcom.co
cpcalendars.wizcom.co
cpcontacts.wizcom.co
display.wizcom.co
forms.wizcom.co
janet.wizcom.co
lw1.wizcom.co
lw2.wizcom.co
lw3.wizcom.co
mail.wizcom.co
ns1.wizcom.co

Showing 12 of 84. View all subdomains →

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • ns1.wizcom.co
  • ns2.wizcom.co
  • ns3.wizcom.co
  • angelina.ns.cloudflare.com
  • jack.ns.cloudflare.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

MX records

  • wizcom.co

SPF policy

  • a: wizcom.co
  • mx: wizcom.co
  • ip: 100.28.32.149
  • ip: 173.0.50.146
  • ip: 3.213.24.111
  • ip: 38.141.45.210
  • ip: 38.141.45.74
  • ip: 54.86.96.175
  • ip: 69.16.233.58

Threat-feed evidence

History

Related pages

Pivot from wizcom.co 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: "wizcom.co"})-[: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.